Screenshots of Software Localization

This is a Chinese translation of a menu. The translator can type in the sheet, or the editor. The preview shows how the Chinese menu will look like. - Sisulizer supports all languages

Sisulizer's text filter work on context, original string, and translation. The filters work including, and excluding, great for searching inconsistent translations. Search case-sensitive, for whole words, or with wildcards. You can save your custom set of filters for easy access in your localization project.

The new live spell check is smart, and filters accellerators before spell checking. So you don't get much false positives, and do not need to add nonsense to your dictionary

Delphi supports various options to go international. You can compile an executable for each language, ship a multi-language exe, use resource dlls, or even embed them in your executable. No matter which way fits your needs best, Sisulizer supports them all.

This is a Japanese translation of a dialog. The translator can type in the sheet, or the editor. The preview shows how the Japanese dialog will look like. The untranslated strings are displayed in red - Sisulizer supports all languages

Sisulizer can also spell check the original text. Whenever a translator finds spell checking errors in the original he can inform the author by email. Sisulizer never changes the original but can help you generating a better one, too.
And like you can see, the original language can be different from English. In this case we use Sisulizer to localize a German ini file.

This is a Japanese translation of a dialog. The translator can type in the sheet, or the editor. The preview shows how the Japanese dialog will look like. The untranslated strings are displayed in red - Sisulizer supports all languages

XML tags can be selected as localizable. Each XML tag can be segmented deeper. Also nice is that HTML tags are marked, but not visible as pure html. Here you see bold tags in the English original, and the Russian translation.

Detailed statitic report for all languages in your project. For each language you see the number of strings, words, and characters, and more. so you know what your translators did, and what they can charge.

You can configure various options around encoding. In XML it is easy because UTF-8 is used. For use on other operation systems you can specify a different new line character as CR + LF. You may want Sisulizer to set a byte order mark in the output files as well.

Ini files don't need to have the .ini as file extension to be localizable with Sisulizer. The project tree shows the sections of an ini file, the Wysiwyg pane shows the keys to be localized. Sisulizer protects translator for breaking your ini file format; neither the section names nor the keys are editable, just the strings can be translated.

You define which sections of your Ini files are localizable. Only the selected ones a translator can enter a translation. This ensures that your budget does not run out. By using Sisulizer you are sure that no keys or sections disappear or duplicate during translation process.
Besides classical Windows .ini files Sisulizer also supports localization of ini-like files. For easier configuration you can save your set of definitions for later re-use e.g. in other Sisulizer projects by exporting them.