Selected Customers

Specials run until 12/20/2018

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.

Update to Sisulizer 4

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

 

Embedded XML

User interface component properties or string resource items can contain XML data instead of plain text. In most cases this XML data has elements that contain string data. Only the string data need to be localized. The rest of the XML element need to be left at it is. Without embedded XML data feature a single row will contains all raw XML data. This may be very hard to translate and it is also likely that the translated XML data will become invalid. In order to make translation of embedded XML data easy and safe Sisulizer can handle string data as XML. User selects the element that should belocalized and Sisulizer breaks the XML data into several different part. Each part will be on its own row and each part contains plain text that is easy to translate.

Let's have an example. We have a string resource item that contains the following XML data:

<?xml version="1.0"?>
<data caption="Name">
  <code>123</code>
  <header>Report</header>
  <color>0xFFFFFF</color>
  <footer>Internal</footer>
</data>

As you can see the XML contains three elements that need to be localized. If we set the row using XML and mark caption attribute, header and footer elements Sisulizer will replace the original row with three different rows.

Name
Report
Internal

Each row is a separate translation entity and it is translated independently. The advantage of splitting XML data is that in most cases the XML format must be exactly right. If XML data is shows on the translation sheet as it is, it is possible that translator will enter invalid XML format. To prevent that you can make Sisulizer to parse string data as XML.

Sources

Embedded XML and HTML data can be used in the following source types:

Platform Description Sample that demonstrates how to use combined strings
Delphi and C++Builder
Visual C++
Visual Basic
Custom and string resources <sldir>\VCL\Delphi\Combined
<sldir>\VCL\Delphi\StringFormat
.NET Custom and string resources <sldir>\NET\CSharp\Combined
<sldir>\NET\CSharp\Resource
Databases Fields <sldir>\Database\Combined
<sldir>\Database\Structured