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

 

Source | Encodings

Use this sheet the specify the language and encoding properties.

Original language

Specifies the original language of the source. This tells what language is used in the original file or database. If the original item contains two or more languages mixed together set the language that is most widely used.

Original encoding

Specifies the original encoding (i.e. character set) that is used in the original file or database.

Default language

Specifies the default language. This languages is used in the build process if there is no translation given in the project sheet. The translation select rule is following. Use first the translation given in the language column of the build language. If there is no translation then use the country neutral column (if the build language is country specific and a country neutral column exists). If this value is empty too then use the translation given in the column of the default language. If no translation is found then the original value is used.

For example if the project contains English, German and German (Switzerland) and the build language is German (Switzerland) and the default language is English the search order is German (Switzerland) - German - English - original.

Default new line

Specifies the default new line encoding. It is used if the original data does not contains new lines but the translated data contains. Possible values are:

Value Description
Line feed Single line feed character (0A or 000A) are used to mark a new line
Carriage return Single carriage return character (0D or 000D) are used to mark a new line
Line feed + Carriage return Line feed and carriage return characters are used to mark a new line
Carriage return + Line feed Carriage return and line feed characters are used to mark a new line

Read more about new lines.

Language and encoding list

Contains a encoding list. With some sources multiple encoding can be used. By default the most common encoding is used. However you can change the encoding by right clicking the item and selecting a new value. In some sources such as Delphi and C++Builder the encoding can not be set. In those cases this list is not shown.

Use byte order mark

Specifies if Sisulizer includes the byte order mark (BOM) in the beginning of UTF-8 or UTF-16 file when writing files. The following table contains BOM used with each file format:

Format BOM Description
UTF-8 0xEF, 0xBB, 0xBF UTF-8 is byte order insensitive but BOM is used to make difference between code page based text files and UTF-8 based text files.
UTF-16LE 0xFF, 0xFE Little endian UTF-16 text file.
UTF-16BE 0xFE, 0xFF Big endian UTF-16 text file.
Code page N/A BOM is not used with code page based text files.