| Supported File Formats |
|
|
|
Executable Win32 filesRadialix 2 localizes executable files in PE32 and PE32+ (*.exe, *.dll, *.ocx, etc). The program supports localization of files that run under Windows 9X/ME/NT/2000/XP/XP64, as well as Windows CE, Windows Mobile since executable files have a similar format in these systems. Radialix 2 allows the user to edit resources of strings, dialogs, menus, icons and images. To edit dialogs and menus, the program offers a visual designer. The user can also change properties and style of controls in dialogs and change the dialogs themselves using the Properties Inspector. You can add your own controls for text display into a dialog (this feature is often used to show the information about the author of the translation). Graphic resources can be edited in external image editors. Radialix 2 creates the following types of localized files:
Executable files created in Borland Delphi and C++ BuilderRadialix 2 can localize resources of VCL forms from the RC_DATA section. In addition to resource extraction, the program extracts information about the structure of classes from RTTI data, contained in the section of the code. This data is used to display and edit forms correctly in the visual editor. When RTTI data is missing, Radialix uses RTTI data of VCL Delphi 2007. For example, this may occur when the user localizes packed files or resource libraries. The visual designer and Property Inspector are used to edit forms. The user can edit almost all types of properties and add TLabel, TStaticText and TPanel components to the form. Radialix 2 uses data from DRC files to ensure correct work with strings from RC_STRING (resourcestring). DRC files are built in Delphi/C++ Builder. A DRC file is used to get string names by their indexes. Radialix 2 can also localize BPL libraries and executable files, which are compiled using BPL libraries. For the files of this type, Radialix can create resource libraries and localized files, including multilingual ones. Binary Win32 files (.res)This type of files has the extension – .res and contains the same data as resource sections in executable files. The user can create only localized files for this type of files. .NET assembliesRadialix 2 can localize assemblies created in .NET Framework and .NET Compact Framework versions 1 - 3.5, including those assembles that have no support for loading resources. In the latter case, Radialix embeds the code required for loading resources into the localized file automatically when this file is created. Because a .NET assembly is a PE file, Radialix can extract and edit resources from metadata, as well as usual Win32 resources. To edit forms and components, you can use the visual editor and properties inspector from the set of standard components provided by .NET Framework 2.0. Radialix 2 creates the following types of localized files:
.NET Binary Resource FilesA .NET binary resource file is one of the formats of resource files in .NET Framework. Usually files in this format are used to store resources inside .NET assemblies and saved as an image of a file in an assembly. The file extension is “.resources”. To localize .NET binary resource files, Radialix 2 can create localized resource files and .NET resource assembly files. Configuration files in INI formatA file in the INI format is a text file, which consists of sections and lists of parameters (.ini, .lang, and other file types). The name of a section is enclosed in square brackets. A parameter is set as: <parameter name>=<value>. Radialix 2 supports parameters that take several strings and combines parameters with a slash (\) in the end of a string. Comments are supported too. Usually comments start with a semicolon (;). However the user can set any other symbol in the File Properties dialog. File encoding is determined automatically, or it can also be set manually. For INI files, Radialix 2 can create only one file type – a localized file. |