• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Unicode settings

V

Viking77

Messages
139
I have discovered that some of the missions I build here in Canada, when loaded on European or Asian versions of FSX, fail to load properly. Apparently this is an issue of the unicode setting? Is there a "Regional" setting I can use when building the missions that will avoid this p;roblem? thanks!
 
Hi Folks

Viking -
Are you still using the RTM SDK,
or copying an old xml as a template ?

FSX RTM mission xml used Windows-1252 encoding, (Latin alphabet).
SP1 and onwards use UTF-8 encoding, (Universal Character Set).

AIUI
this was to support localization of character sets.

Ensure you are using a UTF-8 encoded .xml template.

HTH
ATB
Paul
 
Last edited:
saving XML

So, saving a new file from within the mission editor (SP2) doesn't take care of the issue? It seems that converting to SPB might help. Do you know what particular elements of the file would have to change when there is a problem? thanks
 
Hi Folks

Viking -
SPB is not conversion.
it's only a compiled version of the xml.



Do you mean the FSX SDK Object Placement Tool ?
You'd need to check -
- ISTR it doesn't convert old 1252 xml.
- New mission xml are UTF-8



Open your .xml in Notepad, (not Wordpad or Word).
For a UCS, you should see -
Code: 
<?xml version="1.0" encoding="UTF-8"?>


EDIT -
Deleted irrelevant potentially misleading info.



HTH
ATB
Paul
 
Last edited:
text editor

thanks Paul, neither NOTEPAD nor TEXTPAD shows those characters in my files. What editor do you recommend?
 
Hi Folks

Viking -
My apologies,
Notepad should be fine,
as it automatically handles those characters.

Notepad should also handle conversion properly.

Open your mission file,
and save as encoding UTF-8.

I've edited my misleading previous post.

HTH
ATB
Paul
 
Notepad

Ah, thanks, yes I see that the files are being saved automatically as UTF-8. Oddly, not all files saved in this format read correctly in other regions. I have one mission, for example, that will not load correctly on some Asian machines unless I first save it as SPB. It reads as UTF-8. Really don't understand what is up with this.. I wonder if it could have something to do with the FLT file? Attached is the XML in question.
 

Attachments

Hi Folks

Viking -
Can you detail the Asian machine's language/charsets ?


Nothing obvious.
Could it be your use of escaping ?
Code: 
Beautiful day. I&apos;ll give Taku Lodge a ring.

Code: 
Ah.. doing well here. We&apos;re inbound with twelve heavy weights. How&apos;s the fishing?



Out of interest -
Are you using some kind of script generator,
or template system to create that mission ?



HTH
ATB
Paul
 
Last edited:
char sets

I'll check on the character sets. No, it's not the &apos; that's a problem.. other missions load fine. But yes, I did build one mission that I used as a template, usually do this a couple times for any mission set. Thanks for your help btw
 
The last part of that isn't entirely true, we are DBCS/MBCS aware, allowing non-ascii chars for Japanese and Chinese languages for example (since FS5 under DOS no less :-> ). We had just about finished making FSvNext true Unicode throughout, now we'll never see it :-<

Tim
 
DBCS support does indeed allow FS to handle a subset of the Unicode characters that is larger than the ASCII characters set, but as it differs from computer to computer which characters are supported you can't use them if you want your addon to work outside your own region.

The only characters you know all FS installs will support are the ASCII characters.
 
Im not sure if this can help I have met the situation that the degree sign of the lantitude and longtitude makes the position wrong. I use simple chinese XP system. When I entered the correct coords and saved. The FSX then made all to N40?00'00" E116?00'00" Th charactor * was changed to? But if I chang all the "?" to a space charactor, the problem disapeared.

Anyone knowes why?
thanks
 
This would indicate that the * you used was not the same as the one present in ASCII. It might be a slightly adjusted * with better spacing for Chinese or something like that.
 
You must log in or register to reply here.
Back
Top