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]

Online Help Source | File

Use this sheet to specify a file to be localized and the location and naming of the localized files that Sisulizer creates.

File name

Type the file name, or press the "..." button to browse to a file. The file must be an online helpfile (e.g. C:\Samples\Sample.hhk).

Output directory

Specifies the directory where Sisulizer creates localized files. By default the output directory is usually the same directory where the original source file is located. You can change this by pressing ... and browsing another directory.

Output files

Specifies what kind of output files Sisulizer creates and what kind of file name it uses when creating those files. Combo box is used to specify the name of the output file. You can select a pattern from the combo box list or you can type your own pattern. Each pattern can contain file and language parameters.

File parameters are:

Parameter Description
<file> Variable is replaced with the original file name with extension.
C:\MyFiles\Sample.exe -> Sample.exe
<dir>

Variable is replaced with the relative directory to the source file including the last backslash.
If the source file is
C:\MyFiles\*.html
and if the file to be processed is
C:\MyFiles\SubFiles\Sample.html
variable is replaced with
SubFiles\
If the file locates in the same directory as the source directory this parameter is ignored.

<body> Variable is replaced with the original file name without extension.
C:\MyFiles\Sample.exe -> Sample
<name>

Variable is replaced with the fixed name of the file or original file extension without period (if the file does not have a fixed name).
C:\MyFiles\Sample.exe -> MyName
Fixed name is a name determined by the original platform and it can not be fixed (e.g. .NET specifies assembly name in the project file and that name must be used in order to enable satellite assembly file).

<ext> Variable is replaced with the original file extension without period.
C:\MyFiles\Sample.exe -> exe

If pattern does not contains <dir> parameter Sisulizer automatically adds it into the beginning of pattern before processing it.

Language parameters are:

Parameter Description
<sl> Sisulizer's locale code is used.
For example "en" is for English, "en-US" is fo English (United States), and "zh.tra" is for Traditional Chinese. The default Chinese script is the Simplified Chinese. This is why the language code of Traditional Chinese is "zh.tra".
<iso> ISO locale code is used. It is combination of language and country. The syntax is
la[_co[_variant]]
where
la ISO-639 language code
co ISO-3166 country code
variant ISO variant code
For example "en" is for English, "en_US" is fo English (United States), and "zh_TW" is for Traditional Chinese. ISO language code does not have any way to code a country neutral Traditional Chinese. That is why Chinese (Taiwan) is used.
<net> NET culture code is used. It is combination of language and country. The syntax is
la[-co[-script]]
where
la .NET language code.
co .NET country code
script .NET script code
For example "en" is for English, "en-US" is fo English (United States), and "zh-TW" is for Traditional Chinese. .NET language code does not have any way to code a country neutral Traditional Chinese. That is why Chinese (Taiwan) is used.
<win> Windows locale code is used. It contains two or three upper case characters.
For example "EN" is for English, "ENU" is for English (United Stated), and "CHT" is for Traditional Chinese.
<mfc> MFC locale code is used. It contains three upper case characters.
For example "ENE" is for English, "ENG" is for English (United Kingdom), and "CHT" is for Traditional Chinese.
<nls> Windows locale id is used. It is a integer number containing the primary and sub language ids.
<hex> As above but four digit hex value is used instead decimal value.

For example if the original file is C:\MyFiles\Sample.xml and the pattern is <body>_<iso>.<ext> the German (Austria) file will be C:\MyFiles\Sample_de_AT.xml.

For example if the original file is C:\MyFiles\Sample.xml and the pattern is <sl>\<file> the Chinese (Taiwan) file will be C:\MyFiles\zh.tra\Sample.xml.