This content has been marked as final. Show 13 replies
Hay Xcalibur, i cannot see a change in the naming of the sprites.
in the first gif you show "Member" in the score, in the
second "Blend". Switch an the campare if anything has changed.
2. if you work only in english, the suggested Latin-1 is ok.
Please note "Junior Member"
Thanks wherold for pointing that out. It now makes perfect sense.
In regards to my second question....
This product is currently going to only be in English. However, it is highly likely that this will have to be localized in other languages, most likely Spanish and possibly Russian. Our other products are also available in about 13 other languages.
i have a project, that is used to be in chinese ( i am from Austria ),
so i use UTF-8 as standard.
You should use "ARIAL UNICODE MS" as default font for the scripteditor, then you can see all output and input in the messagewindow with the right signs too.
JUNIOR MEMBER must not mean that you are a beginner.
Everyone with viewer posts than 30 i think is a Junior.
I am a beginner...
Once you choose the code page to use how do you go back and modify it? Lets say I choose Latin-1 but than have to localize to something like Russian and need to use something differant. Cany you modify the code being used?
You do not need to change the codepage. The reason it asked you about
it to begin with is that it wanted to know what codepage the original
D10 version was made in so it could bring the text in correctly. Now
that it is in, you don't need to set the codepage or anything. Director
does the rest for you.
Thanks for you reply...
How can you tell what was used in the D10 version? One of the reasons we upgraded to D11 was the unicode support for our localizing for Russian languages. Should we be choosing something other than what was used in the D10 versions when upgrading the .dir for these languages?
No. You just choose whatever type the original D10 version was. You
don;t need to worry about the codepages at all ever apart from once
during the D10->D11 conversion process. Once it is in D11, then it is
something that you never need to think about again. It is just so D11
knows how to bring in the text that existed in D10. It has nothing to
do with future deployment options.
If you authored the D10 piece on a Mac, then you would choose "Mac
-"<Language>. If you authored the D10 piece on a PC, then it will be
different for different languages, and I don't know what it would be
apart from US English which would be codepage 1252 (ANSI-Latin I).
This is PC
Got the (ANSI-Latin 1) down. We have a project that in D10 we had to localize in Russian. Problem is that D10 did not support that code to display Russian correctly when working within D10. This support is in D11.
So if I understand you correctly D10 is in ANSI-Latin 1. This is confusing cause when we upgrade the files it defaults to some Turkish code page. Does D11 auto read this formating when upgrading the files and if so should we be allowing the default or should we be telling D11 to use ANSI-Latin 1?
D11 will choose the default code page for the computer you are running
on. It can not read the codepage that was used in D10, which is why it
asks you about it. It tries to be helpful by automatically preselecting
the one it would use if you made the program on that machine. In the
case of most English language developers, it works well. In the case of
non-English developers... not so much.
Thank you for your help!