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.
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
4/23/2012
The new build comes with many new features. [more]
11/9/2011
Sisulizer version 3 out now. [more]
9/30/2011
You are looking for tips and tricks around Sisulizer? [more]
9/8/2011
Delphi Tage 2011 in Cologne are sold out! [more]
8/12/2011
Please us a download manager for your download. [more]
Use this sheet to specify the script options of HTML localization options.
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 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.
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. |
There are two kind of tags. They are:
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.
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
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
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.