Selected Customers
Specials run until 2/20/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
Source | Encodings
Use this sheet the specify the language and encoding properties.
Original language
Specifies the original language of the source. This tells what language is used in the original file or database. If the original item contains two or more languages mixed together set the language that is most widely used.
Original encoding
Specifies the original encoding (i.e. character set) that is used in the original file or database.
Default language
Specifies the default language. This languages is used in the build process if there is no translation given in the project sheet. The translation select rule is following. Use first the translation given in the language column of the build language. If there is no translation then use the country neutral column (if the build language is country specific and a country neutral column exists). If this value is empty too then use the translation given in the column of the default language. If no translation is found then the original value is used.
For example if the project contains English, German and German (Switzerland) and the build language is German (Switzerland) and the default language is English the search order is German (Switzerland) - German - English - original.
Default new line
Specifies the default new line encoding. It is used if the original data does not contains new lines but the translated data contains. Possible values are:
| Value | Description |
|---|---|
| Line feed | Single line feed character (0A or 000A) are used to mark a new line |
| Carriage return | Single carriage return character (0D or 000D) are used to mark a new line |
| Line feed + Carriage return | Line feed and carriage return characters are used to mark a new line |
| Carriage return + Line feed | Carriage return and line feed characters are used to mark a new line |
Read more about new lines.
Language and encoding list
Contains a encoding list. With some sources multiple encoding can be used. By default the most common encoding is used. However you can change the encoding by right clicking the item and selecting a new value. In some sources such as Delphi and C++Builder the encoding can not be set. In those cases this list is not shown.