Nos principaux clients

Acheter maintenant

Les offres sont destinées aux clients commerciaux et industriels.
Tous les prix sont nets.

Grille tarifaire complète.

Vous n'êtes pas sûr du choix de votre édition ? Visitez notre tableau Comparatif des éditions

Mise à jour à la 4

Sisulizer 4 is a payés mise à jour recommendée pour tous les clients de Sisulizer 1.x, 2008/2010 et 3.

Update to Sisulizer 4

Vous utilisez encore Sisulizer 1.x, Sisulizer 2008/2010 ou Sisulizer 3?

Il est temps de mettre à jour à la version 4 pour profiter des nouvelles fonctions des versions 4.

News sur le logiciel de localisation

Version 4 Build 369 libéré

6.10.2017

La nouvelle version a de nouvelles fonctions. [plus]

Sisulizer 4 Build 366

1.3.2017

Build 366 - support for Visual Studio 2017 [...]

10 Years Sisulizer

5.8.2016

Celebrate and save Big. [...]

Delphi Berlin, Android, Project Merge...

6.5.2016

Build 360 [...]

Delphi 10, VS 2015, .NET 4.6

14.10.2015

Up-to-date for the future. [...]

Nos clients utilisent Sisulizer...

portée clients internationaux avec le logiciel dans leur langue

pour localiser leurs interne logiciel dans les filiales internationales

construire multilingue logiciel personnalisé pour les entreprises de leurs clients

comme Les fournisseurs de services de localisation parce que c'est l'outil de localisation de leurs clients

pour localiser le logiciel à gouvernement Agences

À enseigner les logiciels localisation dans les universités

pour la localisation de logiciels sur électronique Dispositifs

Traduction de logiciels pour biomédical Matériel

pour localiser le logiciel dans la Mining L'industrie

créer un logiciel mulitlingual pour mécanique Ingénierie

 

ReportBuilder Source | File

Use this sheet to specify a file or files 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 a ReportBuilder file (e.g. C:\Samples\Project1.rtm).

The file name can contain wild cards (* and ?). When wild cards are used Sisulizer localizes all files matching the file name.

Include sub directories

When checked Sisulizer localized also matching files in every sub directory of the directory that File name specifies.

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.

Use checked language ids

If checked Sisulizer uses checked language ids. This means that if you have a country and script neutral language id on a language that uses two ore more scripts and the platforms language id's do not support scripts Sisulizer when building automatically adds a country part that matches the default country of that language. For example if you have Simplified Chinese id, zh-Hans. When building zh-Hans becomes to zh-CH.

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
<parent>

Variable is replaced with the parent path of the original file.
C:\Files\MyFiles\Sample.exe -> C:\Files
Output directory is ignored.

<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), "zh" is for Simplified Chinese, and "zh.tra" is for Traditional Chinese. The default Chinese script is the Simplified Chinese. This is why the language code of Traditional Chinese has a script part "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.
<ish> As above but separator is hyphen (-) instead of underline (_). 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 in .NET 4.0 and later is:
la[-script][-co]

or in .NET 2 and 3.x:

la[-co][-script]
where

la .NET language code.
script .NET script code. .NET 4 uses the standard script codes such as Hans, Hant, Cyrl, Latn, etc. .NET 2-3 uses legacy Chinese codes such as CHS and CHT.
co .NET country code
For example "en" is for English, "en-US" is fo English (United States), and "zh-Hant" is for Traditional Chinese. In .NET 2 and 3.x "zh-CHT" is for Traditional Chinese.
<tag>

IETF language tag code is used. It is combination of language, script and country. The syntax is:
la[-script][-co]
where

la ISO-639 language code
script ISO 15924 script code
co ISO-3166 country code
For example "en" is for English, "en-US" is fo English (United States), and "zh-Hant" is for Traditional Chinese.
<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.