Use this sheet to specify a file to be localized and the location and naming of the localized files that Sisulizer creates.
Type the file name, or press the "..." button to browse to a file. The file must be a Windows binary file created by C/C++ compiler (e.g. C:\Windows\Notepad.exe) and using the standard WIN32 resources or MFC resources.
The file must be a valid Windows PE file. If you use any post linker tools such as compresser or encrypter do not apply the tool for this file but the localized output files created by Sisulizer.
Specifies the directory where Sisulizer creates localized files. By default the output directory is usually the same directory where the original source file is located. You can change this by pressing ... and browsing another directory.
Specifies what kind of output files Sisulizer creates and what kind of file name it uses when creating those files. You can check one or more output file types.
| Output file type | Description |
|---|---|
| Localized files | If checked Sisulizer creates a localized file for each language in the project. For example if the original file is MySample.exe and the project contains German and Japanese, Sisulizer creates de\MySample.exe and ja\MySample.exe. These files are equal to the original file except resource data has been localized. |
| Multilingual file | If checked Sisulizer creates one multilingual file containing all the languages of the project. For example if the original file is MySample.exe, Sisulizer creates all\MySample.exe that contains resources in each language of the project. |
| Resource DLLs | If checked Sisulizer creates localized resource DLL files. They are resource-only DLLs that contains the same resource data as the original file but the resource data has been localized to the target language. Delphi and C++Builder (VCL) Use VCL's resource files and Sisulizer VCL functions to enable run-time language switch. For example if the original file is MySample.exe and the project contains German and Japanese, Sisulizer creates Sample.DE and Sample.JA resource DLL files. Visual C++ (MFC) Use MFC's resource files to enable initial language choose. For example if the original file is MySample.exe and the project contains German and Japanese, Sisulizer creates SampleDE.dll and SampleJA.dll resource DLL files. |
| Embedded resource DLLs | If checked Sisulizer creates an output files that contains all the resource DLL files embedded into the original file. Such an EXE can support several language in one file and the user can even change the language of the application on run time. The output directory for the embedded file is "emb". |
Each output file types contains a combo box that is used to specify the name of the output file. You can select a pattern from the combo box list or you can type your own pattern. Each pattern can contain file and language parameters.
File parameters are:
| Parameter | Description |
|---|---|
| <file> | Variable is replaced with the original file name with extension.C:\MyFiles\Sample.exe -> Sample.exe |
| <relativefile> | Variable is replaced with the relative file to the source file. If the source file is C:\MyFiles\*.htmlThen the following file has a sub file part |
| <body> | Variable is replaced with the original file name without extension.C:\MyFiles\Sample.exe -> Sample |
| <ext> | Variable is replaced with the original file extension without period.C:\MyFiles\Sample.exe -> exe |
Language parameters are:
| Parameter | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| <sl> | Sisulizer's locale code is used. For example "en" is for English, "en-US" is fo English (United States), and "zh.tra" is for Traditional Chinese. The default Chinese script is the Simplified Chinese. This is why the language code of Traditional Chinese is "zh.tra". |
||||||||
| <iso> | ISO locale code is used. It is combination of language and country. The syntax isla[_co[_variant]]
|
||||||||
| <net> | NET culture code is used. It is combination of language and country. The syntax isla[-co[-script]]
|
||||||||
| <win> | Windows locale code is used. It contains two or three upper case characters. For example "EN" is for English, "ENU" is for English (United Stated), and "CHT" is for Traditional Chinese. |
||||||||
| <mfc> | MFC locale code is used. It contains three upper case characters. For example "ENE" is for English, "ENG" is for English (United Kingdom), and "CHT" is for Traditional Chinese. |
||||||||
| <nls> | Windows locale id is used. It is a integer number containing the primary and sub language ids. | ||||||||
| <hex> | As above but four digit hex value is used instead decimal value. |
For example if the original file is C:\MyFiles\Sample.exe and the pattern is <file>_<iso>.<ext> the German (Austria) file will be C:\MyFiles\Sample_de_AT.exe.
For example if the original file is C:\MyFiles\Sample.exe and the pattern is <sl>\<filename> the Chinese (Taiwan) file will be C:\MyFiles\zh.tra\Sample.exe.
Specifies how the resource are created. Possible options are:
| Value | Description |
|---|---|
| Resource DLL filename | Speficies the resource only DLL file that is used basic for the localized resource DLLs. If this is left empty the build in resource file is used. |
| Copy all the resources | If checked Sisulizer copies all the resources to the localized resource DLLs. If this is unchecked Sisulizer copies only those resource data that differs from the original resource data (e.g. has been localized). |
| Keep original resources | If checked the multilingual localized file contains the original resources. If not checked the original resources are removed and replaced with localized resources. |
| Embedded resource type | The resource name that is used when adding embedded resources to the output file. Default is SISULIZER. |
| Embedded resource name | The resource name that is used when adding embedded resources to the output file. The string can contain language code variables. Default is <sl> |