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]
Visual Basic Project Source | Options
Use this sheet to specify the Visual Basic localization options.
Context method
Context method specifies how context value of formed. Possible values are:
| Value | Description |
|---|---|
| Item index | Item index is the string context. Each item (code or string) has an index value that is a counting integer values starting from 0. Compared to String value method this method creates own row for each instance of the same string letting you to translate them in a different way. This is the default value. |
| String value | String value is the string context. If the source code contains same string twice of more then all instances share the single row and they all are translated in the same way. |
Both methods can be used with any file. The difference is how duplicates strings are handled. Item index creates as many rows as there are duplicate strings. String value method always only one row for each string.
Show source code to translators in visual editor
Specifies if visual source code editor is displayed or not. Uncheck this is you do not want the translator see your source code.
Note! Unchecking this does not completely remove the source code data from the project file. Even if you uncheck this source code can be extracted from the project file even it is not trivial. If you want to be 100% sure that your source code does not leak do not send Sisulizer project files (.slp) to translators but use TMX or Excel as exchange format.
Exclude those strings that should not be localized
If checked Sisulizer does not locale strings that is in most cases not supposed to be localized. The actual strings depend on the source code type but for example strings in the include file and pragma lines are excluded.
Compile localized project
If checked Sisulizer compiler the localized project to an EXE file.