siComponents 6.0.1

[Kev]

It looks like the Extended Translations String Editor now handles unicode ok.

But, there is still some problem applying the strings to RadioGroups and tntRadioGroups. For example, Russian strings are entered into tntRadioGroup String Editor and they are applied to new RadioButtons in the group with valid captions. Now trying the same thing by creating buttons with English strings using the IDE and then using siComponent's Ext. Trans. string editor to enter Russian Strings (Language 2). It appears to work in the Trans. Editor, but as soon as you save and close it and then switch the ActiveLanguage, the strings displayed for the buttons in the IDE are from some odd char set. Switch back to the Lang. Ed and the strings show perfectly fine in there.
The Char Set and Font properties are configured as needed.

Can anyone reproduce this behavior?

Thanks,
Kev

[isiticov]

Yes, this is know beahvior. This is the problem of the dealing with Ansi conversion, since TsiLang translates TNTWideStrings through their AnsiString property. But the other side of such situation would be that if your user is able to read Russian and his OS has Russian default locale (this is true for most users in the word to have national locale as default one) then he will get exactly what is needed in these strings.

[Kev]

So, in the strict sense, that is not true Unicode behavior which would allow the strings to be displayed regardless of the Locale setting. Correct?

[isiticov]

Yes, absolutely, and when you add AnsiStrings propertyto the list of translations you may notice Anis prefix of property name.
But, actually, we're trying to find a general way to handle Unicode TStrings (such as TTntStrings, TWideStrings and other) properties with TsiLang.