Text data in the localization project is stored in Unicode (in memory – UTF-16; in the project file - UTF-8). This allows the user to store and edit almost all characters, which are used today. When resources are extracted from a localized file, Radialix 2 converts non-Unicode text into Unicode. However when localized files are created, the program converts Unicode text to a non-Unicode encoding. If the program fails to convert characters, it displays a message where it indicates the position with an incorrect character and creation of a file is blocked. This check may occur without creating localized files. The user needs to go to the Checking settings of the Project Properties dialog and tick the Invalid symbol(s) option.

No conversion is executed if text in a localized file is stored in Unicode.

The type of encoding for non-Unicode text in a localized file is determined as follows:

Strings in Win32 resources – default encoding for the language, selected in the Language of Text field in the File Properties dialog. Default encoding is set strictly for each language. You can see it in the language settings (Tools>Options>Languages>Supported languages, CP column).

Text resources in PE files (for example, RT_HTML resources) – encoding is determined automatically by analyzing text. If encoding cannot be determined, Radialix 2 uses default encoding, selected for the language of text and strings. The type of encoding for such resources is displayed in the Original codepage column in the editor:

INI files – the Encoding field on the Source Settings tab in the File Properties dialog:

When localized files are created, Radialix 2 converts to non-Unicode text according to the encoding used by default for the translation language. You can set an encoding for each hard-coded string manually in the Property Inspector (<Default> corresponds to the default encoding for the translation language):

For text files, encoding of the created file is determined by the value of the Encoding field on the Target Settings tab in the File Properties dialog (<Default> corresponds to the encoding of the translation language).

When non-Unicode text is converted, the program displays an error message if a converted character is missing in the codepage. A localized file is not created. It often results from the use of some symbols to display special characters, or signs in the original file. If this error occurs, you need to find an appropriate character in the codepage of the translation language.

Radialix 2 always edits text in the Unicode mode. As the user enters text, the program can check entered characters for availability in the codepage of the translation language (Invalid symbol(s) option in the Project Properties dialog).