Three simple steps to localize
C#, VB.NET, Delphi, FireMonkey, C/C++, Android, VB, Java, XML, Databases, HTML, HTMLHelp, ...
Update to Version 3
Sisulizer version 3 is a paid update recommended for all Sisulizer customers.
Still using Sisulizer 1.x or Sisulizer 2008/2010?
Time to update to version 3 now and profit from all new features in version 3.
Specials run until May, 20 2012
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
Social Networks
(english)Selected Customers
Software Localization News
Version 3 Build 331 released
4/23/2012
The new build comes with many new features. [more]
Top News: Version 3
11/9/2011
Sisulizer version 3 out now. [more]
Tips & Tricks
9/30/2011
You are looking for tips and tricks around Sisulizer? [more]
Delphi Tage
9/8/2011
Delphi Tage 2011 in Cologne are sold out! [more]
Download Build 321
8/12/2011
Please us a download manager for your download. [more]
Database Source | Settings
Use this sheet to specify how to maintain project during the scan process and how to update the localized databases during the build process.
Replace project translations with existing translations in database
Specifies the existing translation will be replaced with the values in the database when scanning the database. Possible options are:
| Never update existing translations | Does not bring any translation from the database to the project. |
| Always update existing translations | Bring translations from the database to the project. Overwrite the existing value if it differs from the value in the database. |
| Update only project empty translations | Bring translations from the database to the project only if the current value in the project is empty. |
Set the value to the second or third value if you have manually modified the localized values in the database and you want to get the modified values from the database to the project.
This option is not enabled if either database cloning is used or segmentation is turned on.
When building incomplete database rows
Specifies how incomplete row should be handled during the build process. Possible options are:
| Value | Description |
|---|---|
| Use original string | Use the original value in the field. |
| Use empty string | Write the empty string to the field. |
| Skip row | Skip the row and does not write anything. |
This option is not enabled if database cloning used.
Other
Check Use Oracle language codes in order to to use Oracle language codes instead of ISO languages codes.
Read more about database localization.