Radialix 2 can run created localized files, as well as source files of a localization project. The settings can be configured in the File Properties dialog on the Run parameters tab. To run non-executable files, the user is required to enter the path and name of an executable file.

Files are launched using the commands from the Debug menu, or on the Debug toolbar.

Host application for native file – path and name of the application to run a source file.

If a source file is not executable (DLL, resource file, text file), the user is required to specify the path to the executable file that runs a source file. Otherwise it is impossible to run a file.

Delete targets before run native – delete created localized files before running a source file. Localized files must be deleted if a source file loads them automatically on launch.

Host application for translated file – path and name of the application to run a localized file.

Parameters – command line settings of the application to run.

Working directory – working directory of the application to run.

The user can enter tags and variables to the fields for file names and working directory. To insert a tag, use the Tag button to the right of the entry field . The name and directory can be specified using the file selection dialog – button . The Preview field displays the path and name of a file generated for English (USA).

To debug localized files, Radialix 2 searches for a resource that causes an application to run incorrectly. The debugging engine runs a localized file, in which half of translated resources in the beginning are replaced with source resources. Once an application stops, the Debug dialog requires the user to answer whether an application runs correctly. Depending on the answer, Radialix 2 makes a decision what part of translated resources contains an error, divides this part into two, replaces translated resources in one of the parts with source resources, builds a localized file and runs the localized application again. The process repeats until the value that contains an error is localized completely. Firstly, the program determines the translation language (only for multilingual files), resource type, resource and value ID inside a resource. Each of these stages can take several steps.