Sisulizer version 3 is a paid update recommended for all Sisulizer customers.
Still using Sisulizer 1.x or Sisulizer 2008/2010?
Time to update to version 3 now and profit from all new features in version 3.
Offers are for commercial and industrial customers only.
All prices are net.
Complete Price Sheet.
Not sure which edition is the right one? Visit our Edition Comparison
4/23/2012
The new build comes with many new features. [more]
11/9/2011
Sisulizer version 3 out now. [more]
9/30/2011
You are looking for tips and tricks around Sisulizer? [more]
9/8/2011
Delphi Tage 2011 in Cologne are sold out! [more]
8/12/2011
Please us a download manager for your download. [more]
Use this sheet to select what part of the project you will be included to the package. You can choose what languages and what nodes will be added there.
Select the output type of the package(s) that Exchange Wizard creates. Possible values are:
| Value | Description |
|---|---|
| Create one package that contains all selected languages |
Wizard creates one single package file that contains all languages that you select. |
| Create several packages, one for each selected language | Wizard creates several package files that each contains only one language. |
Check languages that you want to include to the package or want to exchange. To check all languages right click and choose Select all. To uncheck all language right click and choose Unselect all.
If your package type is Free Edition setup you can select no languages. In that case Sisulizer will make Free Edition setup that contains no project, just Free Edition setup. Normally there is not need to create Free Edition only setup because translator can download the setup from Sisulizer's home page. However the home page always contains the most recent version. If you just want to deploy the same version as you have to your translator without any projects make a package that contains no languages.
Original language is the language that is used in the original files (e.g. those files that you localized). In most cases the original language is also the source language where the translator translates from. For example if your original files are in English and you want to localize to German and Japanese you need to have a translator that can translate from English to German and another translator that can translate from English to Japanese. Usually English is the best choice for original language because it is likely that you can find much more translator from English to your target language as for example from French to your target languages. By setting alternative original language to some other than none Sisulizer does not show the original strings in the original column but translated string in the selected language. This makes it possible to change the translator language pair suitable for your translator.
If your translator can not understand your original language but he or she understand some other language in the project you can turn on alternative original language. Let's have an example. Your original language is Japanese and you want to localized to English, German and Finnish. It is relatively easy to find a translator who can translate from Japanese to English or German. However from Japanese to Finnish is much harder to find. If you have already done English translation you can turn on English as an alternative language. In that case the Finnish translator does not see the original Japanese string but English string and he or she is translating from English to Finnish.
All nodes of the Sisulizer project will be included to the package by default. You can exclude nodes which should not be added. Double click a node to exclude it. When node is excluded a stop sign will be shown before its icon.