Supports TsiLang library

As of version 2.15, Radialix supports TsiLang library files (http://www.tsilang.com).

It supports the localization of SIL and SIB files. DIC and DIX files can be used as translation memory.

Language names in SIL and SIB files can be arbitrary; therefore, in Radialix 2.15, make sure to define a correspondence between the languages in the localization project and those in the file in the resource extraction options for these files.
The File Language Name column displays the string from the language name field in the file. That string may contain any value and even differ from the real language name. Use the contents of the preview table to determine the language in such cases.

The Project Language column is the language name in the localization project.

The Usage field determines how strings of the respective language are used. Available options are:

• Unused — strings are not extracted.
• Source Text — strings are used as source text.
• Translation — import translation. If the localization project does not contain the required language, it will be added to the project.

To convert strings from ANSI to UNICODE, the program uses the default encoding of the target language (Project Language column). The conversion result is appears in the preview table. Should any errors occur when converting characters to UNICODE, the table header will display the error count, and the strings with the errors will be highlighted.

Also, in the file creation properties for the localized SIL and SIB files, define a correspondence between the languages in the localization project and those in the file.

To add a new language to a localized file, leave the value in the Language in Original File column blank; to change — select one of the languages. In the Language Name in Target File column, you can enter any text, which will be saved as language name to the localized file.

If the target language properties are not set in the table, the program uses the language name in English. In such case, if the language is absent in the original file, it will be added to the localized file.

Conversion of character encoding in executable files using the QT library

Localizing hard-coded strings in PE files using the QT library causes a problem related to the fact that QT converts string encoding ASCIIZ using the codec installed within the PE file. Most often, that’s a codec that interprets all strings as ISO-8859-1 (Latin1). Therefore, there is no way to properly display characters in an encoding other than ISO-8859-1, e.g., Cyrillic characters, unless the codec is replaced.

Radialix 2.15 solves the issue by integrating a DLL library that would install the required codec to the localized file. To integrate the codec successfully, the following requirements are to be met:

• The localized file must import the QtCore4.dll library.
• The localized file must not be protected or compressed.

To integrate the codec, enable the Setup Codec property in the target file properties of the QT executable file parser. Thus, when creating a localized file, the program would create a library named QTPatchXX.XXXX.dll in the folder with the localized file, where X would be replaced with a number; e.g., QTPatch32.1251.dll. That library is to be distributed along with the localized file.

Registration key activation

Radialix 2.15 requires an online activation of the registration key at the activation server. Unless the key is activated, Radialix runs in the demo mode only, appending random characters to strings in localized files.

The activation binds the key to computer hardware. Should the configuration of the computer change, a new activation may be required. Activating Radialix on a computer with an unchanged hardware configuration does not cut the number of available activations.

A key can be activated up to three times. If so many activations is insufficient, please e-mail us at CLOAKING and clarify the reasons why you need a greater number of activations.

The current state of your registration key is available in the About dialog on the Help>About menu. Key activation starts by clicking on the Activate button in the same dialog.