Selected Customers
Specials run until 1/31/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. [...]
.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
HTML Source | Scripts
Use this sheet to specify the script options of HTML localization options.
Scripts
Specifies how scripts inside the HTML are localized. Possible values are:
| Value | Description |
|---|---|
| Scan client scripts | If checked Sisulizer localizes client side scripts such as JavaScript and VBScript codes. |
| Scan server scripts | If checked Sisulizer localizes server side scripts such as JSP, ASP and PHP codes. This is available only on dynamic web pages (e.g. .jsp, .asp, .php). |
Tags
Tags can be used to control what strings to localize in the script sections. Tags options are visible only if you have checked either Scan client scripts or Scan server scripts.
Use this sheet to control what strings are scanned from the files and how they are scanned. Tags are used to control the scan process. They are single line comments that contain information for Sisulizer scanner.
Tags usage
Specifies how tags are used when localizing. Possible values are:
| Value | Description |
|---|---|
| Localize all but excluded | Sisulizer localizes all strings except those that have an exclude tag. You can also use information/include tags to give some properties such as comments and maximum lengths. |
| Localize only included | Sisulizer localizes only those strings that have an include tag. |
Tags apply range
Specifies the range where tag is used. Possible values are:
| Value | Description |
|---|---|
| To all strings in the line |
The tag is applied to all strings in the line where tag is. |
| Only the string following the tag | The tag is applied only to the next strings following the tag.tag. |
There are three kind of tags. They are:
Information/Include tags
Information/include tag is used to pass string properties to the project. The syntax is
<comment><tag>[comment string|attribute]... attribute=MaxChars=mc|MaxPixels=mp|Expression="expression"
where comment is the single line comment character (e.g. "//"), tag is a tag string (e.g. slz), mc is the maximum length of the translation in characters, mp is the maximum length of the translation is pixels, and expression is the combined string expression.
The following line has an include tag that makes Sisulizer to scan the string.:
str = "Hello world"; //slz
The following line has an information tag that contains a comment ("Clicking this button opens on-line help") and sets the maximum length to 300 pixels:
str = "Click Help to get more information"; //slz MaxPixels=300 Clicking this button opens on-line help
Following parts are enabled when the Tags usage is set to Localize all but excluded.
Exclude tags
If you want to disable localization of a string, add an exclude tag on the same line where the string is located. The syntax is
<comment><tag>
For example the following line contains SQL statement and it should not be localized. To disable its localization an exclude tag has been added:
str = "SELECT * FROM MyTable"; //noslz
Block exclude tags
You can disable localization of a entire source code block by using begin and end exclude tags. These will disable all lines between these two tags. The syntax is
<comment><begintag>
<ignoreline>
...
<comment><endtag>
For example the string in the following two lines are not localized.
//beginnoslz
str1 = "Do not localize this";
str2 = "Do not localize this either";
//endnoslz
Source code 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.