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, 31 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]
Translation Engines - Translate settings (Sisulizer Translation Memory)
Use this sheet to specify how to select translations when using translation memory to translate projects.
Language match
Specifies how exact language match must be when finding translations. Possible options are:
| Option | Description |
|---|---|
| Use country neutral translations when translating a sub language | If checked Sisulizer uses also country neutral translations in the case there is no country specific translation. For example if this is checked and you are translating a German (Switzerland) column and there is no translation having de-CH language code but there is a translation having de language code then Sisulizer will use it. |
| Use country specific translations when translating the main language | If checked Sisulizer uses also country specific translations in the case there is no country neutral translations. For example if this is checked and you are translating a German column and there is not translation having de language code but there is a translation having German (Switzerland) language code then Sisulizer will use it. |
| Use translations of the same language but different country | If checked Sisulizer uses also translations of the same language but different country in the case there is no country specific translations. For example if this is checked and you are translating a German (Austria) column and there is not translation having de-AT language code but there is a translation having German (Switzerland) language code then Sisulizer will use it. |
Overwrite current strings
Specifies when Sisulizer overwrites the existing translation in the translation engine. Possible options are:
| Option | Description |
|---|---|
| Never | Existing translations are never overwritten. |
| If the status is less or equal to | Overwrites if existing translation status is less or equal to the given status. |
| Prompt before overwrite | Prompts before overwriting existing string. |
| Always | Existing translations are always overwritten. |
Check Write overwritten values to the log to write the overwritten values to log.
Set status of translated strings
Specifies what value the status of the translation is set. Possible options are:
| Option | Description |
|---|---|
| Default | Status is set either to auto translated or best guess depending on the translation method that was used. |
| Set status to | Status is set to the value specified in the combo box. |
| Set the same status as the translation in the translation memory |
Status is set to the value that the translations has in the translation memory. |