Selected Customers

Specials run until 10/31/2021

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


The new build comes with many new features. [...]



Tutorials updated [...]

.NET Support updated


New in May 2018: [...]

Sisulizer 4 Build 366


Build 366 - support for Visual Studio 2017 [...]

10 Years Sisulizer


Celebrate and save Big. [...]

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


What's new in Sisulizer Version 4

Driven by user request

Since the release of Sisulizer 3 we added an impressive list of new features driven by our users request. Now it is time to celebrate this continued improvements with the release of Sisulizer Version 4.

Time to update to version 4 now and profit from all new features in version 4.

Here are the other news in Sisulizer since version 3 was released.


New Platforms

Delphi XE10.1
  • 64-Bit-Windows: Sisulizer can now use up to 4 GBytes when running on 64-bit Windows.
  • Support for Delphi XE7, Delphi XE8, Delphi XE10, and Delphi XE10.1 (Berlin) including 64-Bit support.
  • Support for C++Builder XE7, C++Builder XE8, C++Builder XE10, and C++Builder XE10.1 (Berlin) .
  • Sisulizer fully supports localization of FireMonkey 2. Using this library instead of VCL enables Delphi developers to create multi-platform applications. Currently for Windows, Mac, iOS, and Android.
  • iOS: Support for iOS resource strings added.
  • Support for Visual Studio 2013 and Visual Studio 2015
  • Support for .NET 4.5.1 and .NET 4.6
  • Support for Visual Basic WPF applications
  • Support for TypeScript, a super set of JavaScript
  • Support for Salesforce translation files added.
  • Support for TBX added. You can import translations from a TermBase eXtension file into translation memory or project.
  • Support for Screen saver file (.scr) added.
  • Support for NexusDB added, a popular database for Delphi.
  • Support for Windows 8, Windows 8.1, and Windows 10
  • Improved support for XAML and WPF

Advanced .NET Platform Support

  • .NET: Sisulizer now supports new Chinese resource names like zh-Hans and zh-Hant
  • .NET: Sisulizer now supports Visual Studio files names which includes brackets.
  • .NET: Any individual resource item can be excluded.
  • .NET: Comments from localized .resx files are imported into the translation comment column.
  • .NET: .NET version is used from Visual Studio project file.
  • .NET: Import of existing localized files works if source is a Visual Studio project file.
  • .NET: Sisulizer can now import exisiting localized file into source that is a Visual Studio solution file.
  • .NET: Any CPU option is supported in 4.5 assemblies.
  • .WPF: Sisulizer detects when .Name properties are used by 3rd party components to store caption or title, and scans them alike.
  • .WPF: Title.StringFormat is added to the default scan property rules.
  • .WPF: Sisulizer supports localization of icon resources.
  • Silverlight: Sisulizer can now localize Silverlight libraries.
  • Silverlight: Sisulizer supports all satellite assemblies from multilingual manifest XAP.
  • XAML: XAML resources are supported in Sisulizer binary localization.
  • XAML: xCode elements are scanned correctly.
  • XAML: Sisulizer now fully supports .NET 4.5 and .NET 4.51.
  • XAML: Solution files outside the project's parent directory are now supported.
  • XAML: Sisulizer now parses paragraph element.
  • XAML: Sisulizer now works correctly for untranslated string values.
  • XAML: Scanning of binding values that are inside Setter works in Sisulizer.
  • XAML: Styles and resources can now be localized, even when they are within a TextBlock.
  • XAML: Sisulizer now supports environment variables such as $(MyDir) in the HintPath attribute of an assembly references during compilation.
  • XAML: Sisulizer supports linked Visual Studio project files, even if located outside project directory.

Improved Platform Support

  • Android: When building multilingual apk files and the default language is specified then Sisulizer uses it if there is no translation given.
  • Android: Sisulizer uses the same compression methods as in the original file.
  • Windows RC: linked translated images will be written with right path.
  • Windows RC: New options (Use caption in menu context). By default Sisulizer uses an index for menuobjects without ID (Popup menus for example). This causes on problem when inserting a new popup menu between olds. Using this options the caption on popup menu is used instead of index. Windows resource compiler: Less than original font sized will be changed.
  • Delphi: TLaTranslator can now translate nested frames.
  • Delphi: Sisulizer automatically detects the Unicode mode of XE2 application.
  • VCL: If Font.Size was negative (typically it is positive) Sisulizer changed the value to positive in the localized form.
  • VCL: Sisulizer localizes TImageList even if the localized image has different mask than the original image.
  • VCL: Support for DevExpress's TcxTreeList.Data added.
  • WinForms: Sisulizer scans comment from form resource file (.resx).
  • Windows Forms: Support for DevExpress InformationTips format added.
  • Windows Forms: If Language property of a form was set to other than Default and Options sheet was configured to write all items to localized files the localized files contained the original Language property. This made it impossible to edit the localized resx in Visual Studio.
  • Windows Forms: Support for DevExpress SuperToolTips format added.
  • Windows Forms: System.Windows.Forms.DataGridViewTextBoxColumn.Width property is automatically scanned without a need to add a custom component rule.
  • WinForms: Support for Windows Runtime's .resw files added.
  • C++Builder:Versions from XE up to XE10.1 (Berlin) including 64-Bit are supported.
  • Database: Can handle GUID types as resource ids.
  • Database: Possibility to analyze and localize only one table from the database.
  • Database: Progress bar and possibility to cancel database analyzing.
  • Interbase/Firebird: Other encodings but UTF-8 can be used on localized fields and rows.
  • Delphi: Versions from XE up to XE10.1 (Berlin) including 64-Bit are supported.
  • FireMonkey: Support for multires bitmaps added.
  • Support for TMS Control Pack (VCL) added.
  • Localization of separate Delphi form files (.dfm) added.
  • HTML: title attribute of span tag will be scanned eg. <span title="Hello">...</span>
  • HTML Help: If the original CHM contain binary index then Sisulizer by default does not create binary index into localized CHM file if the code page of the CHM does not match the current system code page of your OS.
  • Java: Sisulizer now parses correctly .properties file where keys use escape character (\) or : is used as separator instead of =.
  • JSON: Unicode escape output encoding added.
  • PO: Now it is possible to scan PO files such way that the msgstr specifies the original value instead of msgid.
  • PO: Rows are not sorted any more but kept in the original order.
  • PO: Sisulizer can handle multiple equal msgids.
  • PO: You can now contol if msgstr of localized PO file contain empty or original value in the case when there is no translation.
  • TMX localization. Context method added. Now context can either be string value or tuid value.
  • XML: Sisulizer can correctly localized unvalid XML files that use unknown entities not defined in DTD.
  • XML: Sisulizer keeps existing translations better if you change your original XML.
  • XML: You can turn off visual editor.
  • XML: 2000 characters restriction turned off by default.
  • XML: Visual editor sometimes did not show the last character if that was very narrow such as a standalone diacritic character.
  • XML: Segmention works also in the case when the selected element has sub elements.

Improved User Interface

  • .HTML: "xml:lang"-attribute in body tag can be localized. By default it is off. You have to turn it on. Right click html-source in the tree. Choose Properties... menu. From Attributes sheet check "BODY xml:lang" check box
  • Old HTML Editor view added. By default it is not visible. To turn it on choose Tools | Editor | HTML Editor... and check Use check box.
  • XLIFF: Run original and run translated implement.
  • Two new validations added: Length in characters and Length in pixels.

Better Usability

  • Setup: Sisulizer setup does not create a new personal directory every time you update the project but keeps the existing one.
  • Sisulizer supports Visual Studio project file that uses environmental variables.
  • Speed up loading of Sisulizer project containing several Delphi sources.
  • Sisulizer can import translation from localized DFM files.
  • Selectable translation statuses for output files, eg depending on the language.
    Specify translation status for building
  • Support for Microsoft Translator improved to support client id/secret.
  • Embedded XML element editor added.
  • Spell checking: Newest Hunspell library taken in use.
  • When importing an old project that contain a node that no longer exists into the current project Sisulizer now shows the full context of the unknown node.
  • Import Wizard tries to import .resx into selected node of the project tree. If this fails the normal method is used to search the right node to import to.
  • Importing. Sisulizer can now correctly import segmented text after you have changed sources segmentation method.
  • Sisulizer can now properly import data from an import source even when orignal language is not specified.

Better Overall Value

  • User can choose the scope of pseudo translation.
  • If desktop file is invalid a warning message is given.
  • Each row has now two new properties: Created and changed times. Created time shows the date/time when row has been created. Changed date show the date when its original value has been changed. You can filter rows also by there new parameters.
  • Excluded source will not be scanned to speed up scanning.

Extended Automation for Better Integration in Build Process

  • SlMake: When importing SlMake can now map language smarter if there is not exact match. A sub language maps to main language (pt-PT -> pt) and vice versa.
  • SlMake: When you add a new source the initial properties will be same as when using Sisulizer.exe.
  • SlMake: origlang and outitem options added to add task.
  • SlMake: config option added to create task.

You can read about the new features in previous versions (Version 1, V2008, V2010 , Version 3) of Sisulizer.