Selected Customers

Specials run until 12/20/2018

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.

Update to Sisulizer 4

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

 

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.