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
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.
Version 4 Build 374 released
11/30/2018
The new build comes with many new features. [...]
Tutorials
3/5/2019
Tutorials updated [...]
.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. [...]
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
Combined Strings is a feature that breaks a string to parts. This means that a single text will be split into several parts. Combine string rule decides how the breaking is done. Sisulizer uses regular expressions to describe breaking rules. After converting a plain string into a combined string, Sisulizer project will have several rows instead of one single row.
Let's have an example. Before taking combined string in used our project contains the following row:
One;Two;Three
As you can see the string contains three sub strings separated by semi colon. If we set the row using combined string and #;#;#
regular expression Sisulizer will replace the original row with three different rows.
One
Two
Three
Each row is a separate translation entity and it is translated independently. The advantage of combined string is that in most cases the string format must be exactly right. For example if must contain the specific separator characters. If the string is shows on the translation sheet as it is, it is possible that translator will enter string in invalid format. To prevent that you can split combined strings into plain part using expressions.
Let's have few combined string expression examples:
Expression | Sample string | Strings |
---|---|---|
#;#;# | One;Two;Three |
One |
"#" | "This is a string" |
This is a string |
Combines strings can be used in the following source types:
Platform | Description | Tagging | Sample that demonstrates how to use combined strings |
---|---|---|---|
Visual C++,
Visual Basic Delphi, C++Builder |
String resources | No | <sldir>\VCL\Delphi\StringFormat |
.NET | String resources | Yes if project localization is used |
<sldir>\NET\CSharp\Combined <sldir>\NET\CSharp\Resource |
Databases | Fields | No | <sldir>\Database\Combined <sldir>\Database\Structured |
Ini | Values | No | <sldir>\Text\Ini\Combined.* |
Source code | String values | Yes | <sldir>\Source\Pascal.* |
XML | Values | No | <sldir>\XML\Combined.* |
There are several ways to turn combined string parsing on.
You select what rows contain combined string. Right click on the left side of a row in the translation sheet and choose Set Format | Combined and enter the regular expression in a dialog that appears.
You select a part of data structure that always contains combined strings. If you localize an XML file you can select what XML elements contain combined data. If you localize a database you can select what database fields contain combined data.
You select that strings contains combined string as you write you resources or source code. Add tags into your source code or resource file to make Sisulizer automatically apply regular expressions.