Please browse the screenshots of various localization features. This page shows
just a small but interesting part of each screenshot. Just click
on them to view the full size version.
This is a html file in preview mode. This new mode implemented as
tab gives the translator a better impression how the localized
html will look like. - Sisulizer supports the preview in all languages,
here a German localization.
HTML preview in Sisulizer - click screen shot to enlarge
Search Translation Memory
New integrated Translation Memory editor includes a language-dependant
full text search for original and/or translated strings.
Sisulizer offers automatically the language pairs you saved to
your translation memory. - Here we searched a string in all languages.
Searching translation memory contents in Sisulizer - click screen
shot to enlarge
Translation Memory Editor
New integrated Translation Memory editor works
for all available language pairs. You can edit, add, or remove
TM entries. - Here we scroll through English to Arabic translations.
Editing translation memory entries in Sisulizer - click screen
shot to enlarge
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
Chinese menu in Sisulizer - click screen shot to enlarge
Filters that are loved by translators and localization engineers
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.
Text filters with various options - click screen shot to enlarge
Live spell checking is smart
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
Live spell checking is smart - click screen shot to enlarge
Multilingual EXE or DLLs
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.
Single language exes, multilingual exe, resource dlls or embedded resources.
Sisulizer supports all options your platform supports, here Delphi - click
screen shot to enlarge
Silverlight Assembly Linker
Pass your key file to the Assembly Linker for delay signing.
Silverlight localization project options - click screen
shot to enlarge
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
Japanese dialog in Sisulizer - click screen shot to enlarge
You can use Sisulizer to find spelling errors in your original
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.
Typically your translator sees your spell check errors first - click screen shot to enlarge
Encodings, and more
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.
You can configure various options around encoding - click screen shot to enlarge
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.
Content of XML tags can be localized in any language, here Russian - click screen shot to enlarge
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.
Ini file sections are shown in the project tree - click screen shot to enlarge
Localizable Ini sections
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.
Ini file localization with Sisulizer is save - click screen shot to enlarge
Detailed statistic 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.
Project statistics, like word counts - click screen shot to enlarge