Selected Customers
Specials run until 1/31/2019
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
Update to Version 4
Sisulizer version 4 is a paid update recommended for all Sisulizer customers.
Still using Sisulizer 3 or Sisulizer 1.x/2008/2010?
Time to update to version 4 now and profit from all new features in version 4.
Software Localization News
Version 4 Build 374 released
11/30/2018
The new build comes with many new features. [...]
.NET Support updated
6/14/2018
New in May 2018: [...]
Sisulizer 4 Build 366
3/1/2017
Build 366 - support for Visual Studio 2017 [...]
10 Years Sisulizer
8/5/2016
Celebrate and save Big. [...]
Delphi Berlin, Android, Project Merge...
5/6/2016
Build 360 [...]
Our customers use Sisulizer...
to reach international customers with software in their language
to localize their in-house software in the international subsidiaries
to build multilingual custom software for their clients' enterprises
as Localization Service Providers because it is the localization tool of their customers
to localize software at Government Agencies
To teach software localization at Universities
for software localization on Electronic Devices
To translate software for Biomedical Hardware
to localize software in the Mining Industry
to create multilingual software for Mechanical Engineering
Visual XLIFF Localization
XLIFF is a standard format to store data that needs to be localized.
How does Sisulizer localize XLIFF files?
XLIFF file is a bilingual file. It has source and target languages. When Sisulizer reads XLIFF data it reads the source language. Sisulizer goes through every <trans-unit> element in the file and extracts <source> element data to the project.
When Sisulizer writes localized XLIFF files it replaces the <target> element data with data from Sisulizer project and changes the target language of the XLIFF to the current build language. If the file does not contains a <target> element Sisulizer adds it. As a result you will have as many copies of the original XLIFF files as you have languages in the Sisulizer project.
Some XLIFF files contains user interface elements such as dialogs and menus. Sisulizer can read the visual information from such XLIFF files and lets you localize the elements visually. Sisulizer recognizes coord and font attributes in the <group> and <trans-unit> tags.
XLIFF source (and target) tags may contain inline elements. Inline elements are <g>, <x/>, <bx/>, <ex/>, <bpt>, <ept>, <sub>, <it>, <ph>. Sisulizer shows the inline elemens visually in the editing sheet.
Platforms that use XLIFF
Currently XLIFF is not that widely used. Very few tool can export to XLIFF and import it back. However there are few such tools. The following table lists the XLIFF enabled development or authoring tools:
| Tool | Description |
|---|---|
| Adobe Flash | Starting from version 8 it has been possible to export data to XLIFF and import it back. However Adobe's XLIFF import implementation is not a proper one. The importer ignores the target elements and imports source elements instead. This is why you can not use XLIFF localization with Flash language files. You have to use XML localization. Read more about Flash localization. |
If you use above tools you can localize their content by first exporting it to XLIFF, thene using Sisulizer to create localized XLIFF files and finally importing localized XLIFF files back to your tool.