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

 

Visual HTML Localization

HTML localization is very simple in Sisulizer because it is visual, safe and it uses segmentation. Sisulizer extracts the visual HTML data and adds them to the project. When creating localized file Sisulizer creates an identical copy of the original HTML file except it contains is in the target language.

Sisulizer can safely localize also the embedded client and sever side scripts. Use the Scripts sheet of HTML Source Dialog to select what scripts you want to translate and how to translate them.

Formatting tags

In some case several HTML tags should be translated as a single entry. For example you might have text data that contains formatting tags. The following tag contains a plain text:

<p>Finland is the most northern country in the world</p>

If you want to underline the the word most you might store the data in the following way:

<p>Finland is the <u>most northern</u> country in the world</p>

This will break the sentence in three different parts: "Finland is the ", "most" and " country in the world". To translate them separately is impossible or at least very hard. This is why Sisulizer embeds the formatting tags inside a translation unit (e.g. row). When editing the translation Sisulizer shows visually the inline tags. This makes it easy to produce similarly formatted translations.

Segmentation

In many cases HTML contains paragraphs that contains several sentences. In such case Sisulizer by default breaks the paragraphs into segments. Each segment is one translation gentry and it appears on its own row. Segmentation makes translation easier and it also makes reuse of translations much more useful.

Scripts

Sometimes HTML files contain scripts. A script is either a client side (e.g. JavaScript) or a server side (e.g. JSP, ASP) script. Whenever there is a script Sisulizer can use its source code scanner to extract only strings from the code. Translating strings of the source code is much easier and safer than translating the whole source code.

By default Sisulizer scans (and localizes) only those strings that have been marked to be localized. For example if you have the following code:

str = "Hello world";

Sisulizer does not scan it unless you tag it. A tag is a slz comment on the same line as the string.

str = "Hello world"; //slz

You can change the scan logic opposite: to make Sisulizer to scan everything except tagged ones. In this case you have to use noslz tag.

str = "This is not localized"; //noslz

Use the Scripts sheet of HTML Source Dialog to configure how tagging is used.

No matter what your tag mode is you can always use slz tag to give information about strings.

Information/include tag is used to pass string properties to the project. The syntax is

<comment><tag>[comment string|attribute]...
attribute=MaxChars=mc|MaxPixels=mp|Expression="expression"

where comment is the single line comment character (e.g. "//"), tag is a tag string (e.g. slz), mc is the maximum length of the translation in characters, mp is the maximum length of the translation is pixels, and expression is the combined string expression.

The following line has an include tag that makes Sisulizer to scan the string.:

str = "Hello world"; //slz

The following line has an information tag that contains a comment ("Clicking this button opens on-line help") and sets the maximum length to 300 pixels:

str = "Click Help to get more information"; //slz MaxPixels=300 Clicking this button opens on-line help

Preview windows

Shows translated HTML 100% WYSIWYG.

Samples

Sisulizer's HTML directory contains HTML samples.