Selected Customers

Specials run until 10/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 373 released

9/9/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

 

XML Node | Options

Use this sheet to specify the XML file options.

Options

Specifies the formatting options when writing the localized XML files. Possible values are:

Value Description
Keep original format Retain the XML file original format in localized files.
Remove white spaces Remove the leading and trailing white spaces from the elements.
Encode all predefined characters If checked all characters using predefined entities (<, >, ", ' and &) will always be encoded even not necessary needed.

Entities to be processed

Specifies how XML entities are processed. Sisulizer always decodes predefined XML entities when reading an XML file. The following table contains the predefined entities:

Character Name entity Hex entity Integer entity
" &quot; &#x22; &#34;
& &amp; &#x26; &#38;
' &apos; &#x27; &#39;
> &gt; &#x3C; &#60;
< &lt; &#x3E; &#62;

Sisulizer always decodes any hex or integer entity. For example if the XML file contains * it will be read as "*".

When creating localized XML file Sisulizer always encodes & and <. Encoding of other predefined entities depends on their usage in the original file. If the original file has encoded them then the localized files created by Sisulizer use the same encoding. If the original uses several encoding methods Sisulizer prefers name encoding over hex and integer encoding, and hex encoding over integer encoding.

If original XML files contains hex or integer encoding that do not belong to the above predefined entities Sisulizer does never use any encoding when writing characters to the localized XML file. Plain character is written instead.

String entities

If String entities is checked Sisulizer decodes custom string entities when reading the XML file and encodes them when writing the XML file. A custom string entity is a entity defined either in DOCTYPE element or in the DTD file.

<!ENTITY sportname "Downhill skiing">

Whenever an XML element contains &sportname; it will be expanded to Downhill skiing. For example:

<sample>&sportname; is very fast sport.</sample>

will be expanded to "Downhill skiing is very fast sport".

If String entities is unchecked Sisulizer does not decode the string but leaves it as it is. For example the above sample will be read as "&sportname; is very fast sport".

When writing localized XML file Sisulizer does never use string entities but writes plain characters.

File entities

If File entities is checked Sisulizer decodes custom file entities when reading the XML file and encodes them when writing the XML file. A custom file entity is a file based entity defined either in DOCTYPE element or in the DTD file.

<!ENTITY vehicle SYSTEM "Sports.xml">

The content of Vehicle.xml is:

<?xml version="1.0" encoding="UTF-8"?>
  <sport>Skiing</sport>
  <sport>Cycling</sport>

Whenever an XML element contains &sports; it will be expanded to content of Sports.xml file. For example:

<sample>&sports;</sample>

will be expanded to:

<sample>
  <sport>Skiing</sport>
  <sport>Cycling</sport>
</sample>

If File entities is unchecked Sisulizer does not decode the string but leaves it as it is. For example the above sample will be read as will be read as "&sports;".

When writing localized XML file Sisulizer does never use file entities but writes plain characters.

Resource name

Specifies how the localized resource should be named. Possible values are:

Value Description
Keep original name Localized resources have the same name as the original resource.
Add language part A language identifier will be added to the localized resource name. For example Sample.xml will come to Sample.fi.xml when localized to Finnish.