Three simple steps to localize
C#, VB.NET, Delphi, FireMonkey, C/C++, Android, VB, Java, XML, Databases, HTML, HTMLHelp, ...
Update to Version 3
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.
Specials run until May, 20 2012
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
Social Networks
(english)Selected Customers
Software Localization News
Version 3 Build 331 released
4/23/2012
The new build comes with many new features. [more]
Top News: Version 3
11/9/2011
Sisulizer version 3 out now. [more]
Tips & Tricks
9/30/2011
You are looking for tips and tricks around Sisulizer? [more]
Delphi Tage
9/8/2011
Delphi Tage 2011 in Cologne are sold out! [more]
Download Build 321
8/12/2011
Please us a download manager for your download. [more]
Select Exchange Method
This dialog is shown to select the exchange method to be used. Select an appropriate method and press OK. Possible methods are:
| Method | Direction | Translator's tool | Description |
|---|---|---|---|
| Send original project file to translator | developer -> translator | Sisulizer | Send the original project file (.slp) as it is. This is the easiest and fastest way to send data to translator. However the translator will get the whole project including all existing languages and translations. Translator has to have Sisulizer installed or he or she has to install free Sisulizer Free Edition. |
| Send project to translator using Exchange Wizard | developer -> translator | Sisulizer | Use Exchange Wizard to create an exchange package. This takes some time but let you include only those languages and items that are needed. You can also include Sisulizer Free Edition setup to the exchange package. |
| Import translated project file | developer <- translator | Sisulizer | Use Exchange Wizard to import translations from the project file that the translator has sent. After import process developer's projects contains the same translations as the translator's project. |
| Export project and send exported file to translator | developer -> translator | Other | Use Export Wizard to export the project data to another file format such as Excel, Text or TMX file. Send the exported file to the translator. Use this if the translator does not use Sisulizer but some other translation tool. |
| Import translations from a file | developer <- translator | Other | Use Import Wizard to import translations from the translation file that the translator has sent. Use this if your translator does not use Sisulizer but some other translation tool. |
Note! It is highly recommended that Sisulizer is used as translation tool. It is several advantages over TMX, Excel and text files such as visual editors, validations, context sensitive import/export and so on.