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

 

Database Source | Items

Use this sheet to select the database that you want to localize.

Read more about database localization.

Localization method

Specifies the database localization method. This option is enabled only for databases that support database cloning (e.g. Microsoft Access).

Method Description
Use localized items Insert localized data directly into the selected database. The localized data will be added either to localized rows, localized fields or localized tables. Use the Fields and Tables tree to control what items are used.
Clone original database Create localized copies from selected database.

Tables and field

Specifies the localizable tables and fields. Use the mouse to drag and drop the tables and fields and/or right click the mouse button to set the field types. The tree contains several different items. The following table contains the possible items:

Image Name Description
Database The root node that represents the database
Original table Original table.
Localized table A language version of the table. Each original table can contains language specific tables that specify what table is used for each language.
Original field Original field.
Localized field A language version of the field. Each original field can contain language specific fields that specify what field is used for each language.
Marked field A field that has been marked to be localized. This is used in the row and cloning localization methods to mark those fields that should be localized.
Language id field A field that has been marked to be a language id field. This field is used in row localization method to identify the language of the row.
Id field A field that has been marked to be an id field. This field is used in row localization method to identify the resource id in that case where the primary id is not a combination of id and language id fields.
Possible id field A field that can be an id field but has not been marked as an id field. Only one of the possible id fields can be marked as id field.
Comment field A field that has been marked to be a comment field. This field contains comment data.

Id field requires a foreign key check box is used when row localization where id and language id are not part of the primary id is used. If checked the id field has a foreign key. In that case the above tree view does not show integer fields except they have foreign key. If unchecked the id field does not have a foreign key. In that case the above tree shows all integer fields and you have to select what one is the id field. In either way you have to select one field to be as an id field. If there is at least one non-string field that has foreign key Sisulizer will select that as default.