Localize Your software & Increase Your Revenue. When you localize your applications and make them available in new languages, you open new markets and new revenue streams. Sisulizer lets you increase profits by making it easy to offer your software in multiple languages.
Localize your software with Sisulizer, in three simple steps:
· First, scan the application and locate all of the text.
Sisulizer can work directly with your C++ Builder, Delphi, Visual C++, Visual Basic, Java, or windows binary file, or with XLIFF, or with your .NET assembly.
Sisulizer works visually with HTML and XML. Sisulizer can also grab the text from text files, and databases.
Sisulizer can also support mobile applications. Sisulizer supports .NET for Smart Devices, Pocket PC, Windows mobile, Symbian, and J2ME.
· Second, translate the text with Sisulizer's visual editor.
You have complete control over every word to be translated. You can begin the translation work yourself and mark each phrase as having been translated properly, auto-translated, translated by best guess, out for review, or complete.
Use Sisulizer's Exchange Wizard to create and send your translator a single file that contains a self-installing Sisulizer Translation Edition, along with your project file.
When your translator has completed the translation, they run Exchange Wizard to create a single file that they send back to you.
· Third, build the localized version.
Now that your translator has finished translating all of your strings, and you've received your updated file, simply run Sisulizer to build the new version of your program, in the new language.
What's new in Sisulizer 1.6:
Sisulizer 1.6 again improves your localization experience. Here is a list of the most important changes in 1.6:
Text file localization with regular expressions
- Define the translatable contents using regular expressions. With this you can localize more text formats with Sisulizer than ever.
More third party components supported
- Sisulizer 1.6 supports a large list of the most important third party components for .NET and Delphi. You find more details about our third party component support program here.
Improved user interface
-Newcolumns for number of pixels/characters of translation.
- The translation toolbar is now above translation grid making the interface more logical and easier to use.
Improved HTML Help support
- Better WYSIWYG for help contents.
- Localization of auto-generated index entries.
- Faster scanning of large CHM files.
Optimized scanning of HTML files
Improved XML translation support
-More flexible support to better cover different XML structures.
Better INI-file support
- Support for quoted and escaped strings.
Improved IME support
- IME settings are now also saved into general settings as default for new projects.
JSP
- JSP is now better supported. Sisulizer now comes with JSP samples.
- New for the free Translation Edition
- Validation added
-Spell-checking added
- Local DBISAM translation memories access added
New for the Personal Edition
- Validation added
- Spell-checking added
- Local DBISAM translation memories access added
1.6.13 - October 5, 2007:
New features
- You can remove duplicates translations from translation memory using the select translation dialog box.
- Include and exclude tags editing added to Visual Basic source.
- .NET: Embedded XML, HTML, images and binary resources are localized. An embedded resource is a file that is stored as raw data instead of embedding into .resources file.
Improved features
- Wild card (e.g. *.resx) sources no longer contain sub directories that contain no matching files.
- Find and Filter Text: New "Accept wild chars" options. If checked '*' and '?' characters are handled as wild chars.
- "Shift+Del" short cut for excluding rows.
- Short cuts are visible also on popup menus.
- Grid settings in form editor will be saved.
Bug fixes
- .NET: Importing existing translations to a .NET source containing wild card file name (.e.g *.resx) did not work.
- Excluded string were ignored when "Duplicate translation" validation was processed.
- Windows binary: Scanning version resources sometings hangged.
- Windows binary: If project file (.SLP) will be edited in a different file path, the file names of optional header (.H) and resource (.RC) will keep valid.
- .NET. Binary scanning or building sometims caused an error.
- Translations in excluded nodes will be ignored during the building process.
- VCL: If Tlabel control had taRightJurity as Alignment it couldn't be moved horizontally.
