XLIFF Source | File

Use this sheet to specify a file or files to be localized and the location and naming of the localized files that Sisulizer creates.

File name

Type the file name, or press the "..." button to browse to a file. The file must be an XLIFF file (e.g. C:\Samples\Sample.xlf).

The file name can contain wild cards (* and ?). When wild cards are used Sisulizer localizes all files matching the file name.

Include sub directories

When checked Sisulizer localized also matching files in every sub directory of the directory that File name specifies.

Output directory

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.

Output files

Specifies what kind of output files Sisulizer creates and what kind of file name it uses when creating those files. Combo box 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\*.html
Then the following file has a sub file part
C:\MyFiles\SubFiles\Sample.html -> SubFile\Sample.html
<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 is
la[_co[_variant]]
Part Description
la ISO-639 language code
co ISO-3166 country code
variant ISO variant code
For example "en" is for English, "en_US" is fo English (United States), and "zh_TW" is for Traditional Chinese. ISO language code does not have any way to code a country neutral Traditional Chinese. That is why Chinese (Taiwan) is used.
<net> NET culture code is used. It is combination of language and country. The syntax is
la[-co[-script]]
Part Description
la .NET language code.
co .NET country code
script .NET script code
For example "en" is for English, "en-US" is fo English (United States), and "zh-TW" is for Traditional Chinese. .NET language code does not have any way to code a country neutral Traditional Chinese. That is why Chinese (Taiwan) is used.
<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.xml and the pattern is <file>_<iso>.<ext> the German (Austria) file will be C:\MyFiles\Sample_de_AT.xml.

For example if the original file is C:\MyFiles\Sample.xml and the pattern is <sl>\<filename> the Chinese (Taiwan) file will be C:\MyFiles\zh.tra\Sample.xml.