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
PO Source | Options
Use this sheet to specify the PO file options.
Scan comments
If checked Sisulizer reads the comments from PO into Sisulizer project.
Compile
If checked Sisulizer compiles localized PO files to binary MO files.
Use msgstr value as original
If checked Sisulizer uses the value of msgstr as original value instead of the value of msgid.
Include empty translations into MO files
If checked Sisulizer writes also empty translations into MO files. If unchecked item having empty translations are skipped.
Byte Order
Specifies the byte order used in the created MO files. Possible values are:
| Value | Description |
|---|---|
| Little-endian | The least significant byte value is stored at the memory location with the lowest address, the previous byte value in significance is stored at the following memory location and so on. |
| Big-endian | The most significant byte value is at the lowest address. |
Items that localized resource files contain
Specifies what resource items are written to the localized resource files. Possible values are:
| Value | Description |
|---|---|
| Different | If checked Sisulizer does not write resource items to the localized resource file if the value of the item is the same as the original value. Value is not written even if the user has entered the value in the edit sheet if it equals to the original value. |
| Translated | If checked Sisulizer writes to the localized resource file all those resource items that has a translation (i.e. a translation has been given in the edit sheet). This is the default value. |
| All | If checked Sisulizer writes all resource items to the localized resource file. If no translation is entered in the edit sheet the original value is used. The structure of the localized resource files are identical to the original ones. Only the translated values are different. |
If you keep the default value, Translated, Sisulizer can greatly optimize the size of the resource files. This also will fully enable the build-in language fallback of the platform where you application runs. If you choose All no runtime language fallback is done but fallback is done by Sisulizer on build process. We recommend to use either Translated of Different to enabled optimization and language fallback of the platform. When localizing XAML this options is only used with resource dictionaries. All other XAML resources will always contain all items.
Programming language
Specifies the programming language that was used in the application that uses PO files.
Plural forms
For each plural message Sisulizer adds as many rows as specified in this field. If you plan to support only Western and Asian languages 2 is enough. 3 covers most languages excluding Arabic, Slovenian and Welsh. 4 covers all but Arabic. If you want to correctly translate to all Arabic forms set this to 6.