When you perform the build process Sisulizer creates localized files or localized data. Localized files are the localized versions of your original files. The location and format of the localized files depends on the original file. Each platform uses its own localized data. In some cases the localized files equals to the original expect strings are translated into the target language. In that case the file format and extension is the same. Only the location is different.
For an example lets look at Windows application create by Visual C++. The original file might have C:\Files\MyApp.exe. When Sisulizer creates German application it creates German sub directory (de) and creates the German application into that directory. The result file will be C:\Files\de\MyApp.exe. To run your application in German start the German application instead of the original one.
.NET uses uses satellite assembly files for localization. Each satellite assembly file contains resources of the original assembly (e.g. application) but no code. For example if we have C:\Files\NetSample.exe application Sisulizer creates German satellite assembly file C:\Files\de\NetSample.resources.dll. Note that files extension is .dll and the file contains only resource data. You have to deploy both original assembly files and satellite assembly files of your language(s).
By default Sisulizer creates the output files into the default locations. If your platform requires a specific location then Sisulizer uses it. For example .NET resource files must have filename-language.resx and .NET satellite assembly files must have language\filename.resources.dll. If your platform does not have a specific location (e.g. Visual C++) then Sisulizer uses default Sisulizer convention that creates language specific sub directories into the directory where the original file is located and creates output files into sub directories. You can change both the output directory and the output file name by using the File sheet of the source dialog. Right click the original file in the left side project three and choose Properties. Choose File sheet. The sheet contains the original file, output directory and output files.
Output directory specifies the root directory where the output file is created. By default output directory is the directory of your original file. You can change this by typing a new directory or by clicking ... and browsing a new directory.
Output files lets you specify the format and name of the output files. Some platforms support several different output formats. For example when you localize Delphi application the default output file is localized EXE but you can make Sisulizer to create also resource DLLs and/or multilingual EXE. Check the check box of output files that you want to create. 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 contains file and language parameters.
File parameters are:
Variable is replaced with the parent path of the original file.
|<file>||Variable is replaced with the original file name with extension.
Variable is replaced with the relative directory to the source file including the last backslash.
|<body>||Variable is replaced with the original file name without extension.
Variable is replaced with the fixed name of the file or original file extension without period (if the file does not have a fixed name).
|<ext>||Variable is replaced with the original file extension without period.
If pattern does not contains <dir> parameter Sisulizer automatically adds it into the beginning of pattern before processing it.
Language parameters are:
|<sl>||Sisulizer's locale code is used.
For example "en" is for English, "en-US" is fo English (United States), "zh" is for Simplified Chinese, and "zh.tra" is for Traditional Chinese. The default Chinese script is the Simplified Chinese. This is why the language code of Traditional Chinese has a script part "zh.tra".
|<iso>||ISO locale code is used. It is combination of language and country. The syntax is
|<ish>||As above but separator is hyphen (-) instead of underline (_). The syntax is
NET culture code is used. It is combination of language and country. The syntax in .NET 4.0 and later is:
or in .NET 2 and 3.x:
IETF language tag code is used. It is combination of language, script and country. The syntax is:
|<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.|