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

 

PO Source | Options

Use this sheet to specify the PO file options.

Scan comments

If checked Sisulizer reads the comments from PO into Sisulizer project.

Compile

If checked Sisulizer compiles localized PO files to binary MO files.

Use msgstr value as original

If checked Sisulizer uses the value of msgstr as original value instead of the value of msgid.

Include empty translations into MO files

If checked Sisulizer writes also empty translations into MO files. If unchecked item having empty translations are skipped.

Byte Order

Specifies the byte order used in the created MO files. Possible values are:

Value Description
Little-endian The least significant byte value is stored at the memory location with the lowest address, the previous byte value in significance is stored at the following memory location and so on.
Big-endian

The most significant byte value is at the lowest address.

Items that localized resource files contain

Specifies what resource items are written to the localized resource files. Possible values are:

Value Description
Different If checked Sisulizer does not write resource items to the localized resource file if the value of the item is the same as the original value. Value is not written even if the user has entered the value in the edit sheet if it equals to the original value.
Translated If checked Sisulizer writes to the localized resource file all those resource items that has a translation (i.e. a translation has been given in the edit sheet).
This is the default value.
All If checked Sisulizer writes all resource items to the localized resource file. If no translation is entered in the edit sheet the original value is used. The structure of the localized resource files are identical to the original ones. Only the translated values are different.

If you keep the default value, Translated, Sisulizer can greatly optimize the size of the resource files. This also will fully enable the build-in language fallback of the platform where you application runs. If you choose All no runtime language fallback is done but fallback is done by Sisulizer on build process. We recommend to use either Translated of Different to enabled optimization and language fallback of the platform. When localizing XAML this options is only used with resource dictionaries. All other XAML resources will always contain all items.

Programming language

Specifies the programming language that was used in the application that uses PO files.

Plural forms

For each plural message Sisulizer adds as many rows as specified in this field. If you plan to support only Western and Asian languages 2 is enough. 3 covers most languages excluding Arabic, Slovenian and Welsh. 4 covers all but Arabic. If you want to correctly translate to all Arabic forms set this to 6.