Selected Customers
Specials run until 10/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. [...]
Tutorials
3/5/2019
Tutorials updated [...]
.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. [...]
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
Project Wizard - Database (additional)
Use this sheet to select the method how to localize the database and to select the items that will be localized.
Read more about database localization.
Localization method
Specifies the database localization method. This option is enabled only for databases that support database cloning (e.g. Microsoft Access).
| Method | Description |
|---|---|
| Use localized items | Insert localized data directly into the selected database. The localized data will be added either to localized rows, localized fields or localized tables. Use the Fields and Tables tree to control what items are used. |
| Clone original database | Create localized copies from selected database. |
Tables and field
Specifies the localizable tables and fields. Use the mouse to drag and drop the tables and fields and/or right click the mouse button to set the field types. The tree contains several different items. The following table contains the possible items:
| Image | Name | Description |
|---|---|---|
 |
Database | The root node that represents the database |
 |
Original table | Original table. |
 |
Localized table | A language version of the table. Each original table can contains language specific tables that specify what table is used for each language. |
 |
Original field | Original field. |
 |
Localized field | A language version of the field. Each original field can contain language specific fields that specify what field is used for each language. |
 |
Marked field | A field that has been marked to be localized. This is used in the row and cloning localization methods to mark those fields that should be localized. |
 |
Language id field | A field that has been marked to be a language id field. This field is used in row localization method to identify the language of the row. |
 |
Id field | A field that has been marked to be an id field. This field is used in row localization method to identify the resource id in that case where the primary id is not a combination of id and language id fields. |
 |
Possible id field | A field that can be an id field but has not been marked as an id field. Only one of the possible id fields can be marked as id field. |
 |
Comment field | A field that has been marked to be a comment field. This field contains comment data. |
Id field requires a foreign key check box is used when row localization where id and language id are not part of the primary id is used. If checked the id field has a foreign key. In that case the above tree view does not show integer fields except they have foreign key. If unchecked the id field does not have a foreign key. In that case the above tree shows all integer fields and you have to select what one is the id field. In either way you have to select one field to be as an id field. If there is at least one non-string field that has foreign key Sisulizer will select that as default.