Updaten Sie auf Version 3

Sisulizer Version 3 ist ein kostenpflichtiges Update für alle Sisulizer 1.x und 2008/2010-Kunden.

Verwenden Sie noch Sisulizer 1.x oder Sisulizer 2008/2010?

Aktualisieren Sie jetzt auf Version 3 und nutzen Sie alle Neuigkeiten in Version 3.

Angebot gültig bis 20.5.2012

Die Angebote richten sich an kommerzielle und industrielle Kunden.
Alle Preisangaben sind netto.

Komplette Preisliste.

Suchen Sie die richtige Edition? Besuchen Sie unsere Vergleichstabelle

Bitte stimmen Sie für Sisulizer

Bitte klicken Sie diese Facebook-Schaltfläche, um diese Seite mit Ihren Freunden zu teilen

Share

(english) (german)


Drücken Sie bitte die Google +1-

Schaltfläche, um Sisulizer eine positive Bewertung in Googles neuem Bewertungssystem zu geben.

Vielen Dank.

Ausgewählte Kunden

Softwarelokalisierungs-News

Version 3 Build 331 veröffentlicht

23.4.2012

Der neue Build kommt mit vielen neuen Features. [mehr]

Top News: Version 3

9.11.2011

Sisulizer Version 3 ist da. [mehr]

Tipps & Tricks

30.9.2011

Sie suchen nach Tipps und Trick zum Thema Sisulizer? [mehr]

Delphi Tage

8.9.2011

Die Delphi Tage 2011 in Köln sind ausverkauft! [mehr]

Build 321 herunterladen

12.8.2011

Bitte verwenden Sie einen Download Manager. [mehr]

Project Wizard - HTML

Use this sheet to specify how to localize the script elements in the HTML file.

Images

Specifies how HTML images are localized. Possible values are:

Value Description
Scan images If checked Sisulizer scans images of the HTML files making it possible to replace them in the localized files.
Copy images If checked Sisulizer copies original image files to the localized directories.
Update image sizes If checked Sisulizer updates the image size attributes to match the localized image (if any) when writing the localized HTML files.
Update si&zes in image styles If checked Sisulizer updates the image size values in style attributes to match the localized image (if any) when writing the localized HTML files.
For example the size of the original image is 200x100 and the translated image is 210x110.
style="width:200px; height:100px;"
->
style="width:220px; height:110px;"

Text

Specifies how text is written in HTML. Possible values are:

Value Description
Keep format If checked the text preserves spaces and line breaks. Otherwise all extra spaces and all line breaks will be removed on scanned rows.
Keep format in code tags If checked the text enclosed in the code element preserves spaces and line breaks. Otherwise all extra spaces and all line breaks will be removed on scanned rows.

Building

Specifies how HTML file are built. Possible values are:

Value Description
Clean syntax If checked the syntax of HTML-code will be cleaned during the build process. For example if you have an attribute without quotes, Sisulizer add those marks.
For example <h2 align=left> becomes to <h2 align="left">
Add or modify content language If checked the following lines will be added to HEAD-section if the section does not already contain them:
<meta http-equiv="Content-Language" content="fi">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
If the section already contains them Sisulizer just updates the content of the lines.
Set dir attribute for RTL languages (Arabic, Hebrew) If checked the following attribute is set when creating Middle Eastern HTML files:
<body dir="rtl">
If the attribute already exists Sisulizer just updates the value of the attribute.

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.

There are two 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