Selected Customers

Buy Now

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 372 released

5/22/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

 

Property

Use this dialog to add a new property definition to Sisulizer's visual editor.

Name

Specifies the name of the property. The name can contain wild cards (* and ?).

Default Value

Specifies the default value of the property. Use it if the file does not contain properties having the default value.

VCL: In VCL for example the most used values of properties are not saved. Those values are defined as default values. When a property of a certain component is read the default value will be used if no other value has been saved. The default Alignment property of TLabel control is taLeftJustify. This value is not written to the resource file. The other possible values are taCenter and taRightJustify. If value is one of those it will be written to the resource file.

Normally when you map your own Label-control the default value is usually taLeftJustify. On the other hand if you have a component that's default value should be laCenter you should define Default Value as 1 (the ordinal value of taCenter). If not defined Sisulizer will use taLeftJustify as a default value.

Type

Specifies the type of the property. Some resource formats such as VCL contain type information so Sisulizer can figure out the type of the property even it it belongs to a 3rd party component. However XAML (WPF) resource files, .xaml, do not contain type information. If you map a 3rd party WPF component and it contains a custom property that is not a string type, select the type of the property from the combo box.

.NET: This is visible only of the platform does not provide type information of the property. Windows Forms in .NET contain such information but WPF does not. However because a .NEt project can contains mixed Windows Forms and WPF data this type in show even on pure Windows Forms projects.

Mode

Specifies the mode of the property rule. Possible choices are:

Value Description
Excluded Property is ignored when scanning.
Included Property is included when scanning.
Structured data Property contains structured data. Use definitions to specify the data format.

Separate lines

Check this if you want to scan multi line text into separate rows in the project. By default this is unchecked and multi line text is scanned as one entity.

Data Structure Definition

Contains lines that specify the structure of data. Sisulizer can scan the following structured data:

Property Data Description
Combined strings Property contains a string that contains a combined string. Enter the regular expression describing the data in the line(s).
HTML Property contain an HTML file. Enter string 'HTML' to the first line.
XML

Property contain an XML data. Enter one line for each element or attribute that you want to localize. Each line contains the path and name of the element/attribute. Parent and child element are separated by @ character. Attribute name start with # characters. Do not include the name of the root element.

For example if we have the following XML data as property value:

<?xml version="1.0"?>
  <data caption="Name">
  <header>Header</header>
  <footer>Footer</footer>
  <sub author="Writer">
    <value>Value</value>
  </sub>
</data>

and we want to localize strings marked with bold typeface we need to enter following lines:

#caption
header
footer
sub@#author
sub@value