Selected Customers
Specials run until 1/31/2019
Offers are for commercial and industrial customers only.
All prices are net.
Complete Price Sheet.
Not sure which edition is the right one? Visit our Edition Comparison
Update to Version 4
Sisulizer version 4 is a paid update recommended for all Sisulizer customers.
Still using Sisulizer 3 or Sisulizer 1.x/2008/2010?
Time to update to version 4 now and profit from all new features in version 4.
Software Localization News
Version 4 Build 374 released
11/30/2018
The new build comes with many new features. [...]
.NET Support updated
6/14/2018
New in May 2018: [...]
Sisulizer 4 Build 366
3/1/2017
Build 366 - support for Visual Studio 2017 [...]
10 Years Sisulizer
8/5/2016
Celebrate and save Big. [...]
Delphi Berlin, Android, Project Merge...
5/6/2016
Build 360 [...]
Our customers use Sisulizer...
to reach international customers with software in their language
to localize their in-house software in the international subsidiaries
to build multilingual custom software for their clients' enterprises
as Localization Service Providers because it is the localization tool of their customers
to localize software at Government Agencies
To teach software localization at Universities
for software localization on Electronic Devices
To translate software for Biomedical Hardware
to localize software in the Mining Industry
to create multilingual software for Mechanical Engineering
Java Binary Source | File
Use this sheet to specify a file 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 a Java archive file (e.g. C:\Samples\Project.jar).
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.
Use checked language ids
If checked Sisulizer uses checked language ids. This means that if you have a country and script neutral language id on a language that uses two ore more scripts and the platforms language id's do not support scripts Sisulizer when building automatically adds a country part that matches the default country of that language. For example if you have Simplified Chinese id, zh-Hans. When building zh-Hans becomes to zh-CH.
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 |
|---|---|
| <parent> | Variable is replaced with the parent path of the original file. |
| <file> | Variable is replaced with the original file name with extension.C:\MyFiles\Sample.exe -> Sample.exe |
| <dir> | 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.C:\MyFiles\Sample.exe -> Sample |
| <name> | 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.C:\MyFiles\Sample.exe -> exe |
If pattern does not contains <dir> parameter Sisulizer automatically adds it into the beginning of pattern before processing it.
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), "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 isla[_co[_variant]]where
|
||||||
| <ish> | As above but separator is hyphen (-) instead of underline (_). The syntax isla[-co[-variant]]where
|
||||||
| <net> | 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:
|
||||||
| <tag> | 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. |
For example if the original file is C:\MyFiles\Sample.xml and the pattern is <body>_<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>\<file> the Chinese (Taiwan) file will be C:\MyFiles\zh.tra\Sample.xml.