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

 

Import Existing Translations

Sisulizer can import existing translations when creating a new project. The source of the imported translations depend on the sources. The following sources are supported:

.NET

If you add a .resx file, .NET assembly file (.exe or .dll), Visual Studio project file (.csproj or .vbproj), or Visual Studio solution file (.sln) to a Sisulizer project, Project Wizard can import translations from localized .resx files. For example if you have selected MyFile.resx and there exists MyFile.de.resx file, Project Wizard will add German to the project and imports translations from MyFile.de.resx. Localized resource files must locate on the same directory as original one(s).

If you add a .NET assembly file (.exe or .dll) to a Sisulizer project, Project Wizard can import translations from localized satellite assembly files. For example if you have selected MyApplication.exe and there is de\MyApplications.resources.dll file Project Wizard will add German to the project and imports translations from de\MyApplication.resources.dll. Localized satellite assembly files must locate on a country depend sub directory of the directory where the assembly file is located.

Visual C++

If you have existing resource DLL's of a MFC application that you add to a project Sisulizer can import translations from the resource DLL's. For example if you have selected Project1.exe and there exists Project1DE.dll file Project Wizard will add German to the project and imports translations from Project1DE.dll. Resource DLL must locate on the same directory as the application or library file. Sisulizer can also import existing localized files if they are in a sub directories. For example if your original file is Project1.exe and you have de\Project1.exe Sisulizer will import German translations form that file. If you have Project1DE.exe Sisulizer will also import German translations from that file.

VCL

If you have existing resource DLL's of a VCL application that you add to a project Sisulizer can import translations from the resource DLL's. For example if you have selected Project1.exe and there exists Project1.DE file Project Wizard will add German to the project and imports translations from Project1.DE. Resource DLL must locate on the same directory as the application or library file. Sisulizer can also import existing localized files if they are in a sub directories. For example if your original file is Project1.exe and you have de\Project1.exe Sisulizer will import German translations form that file. If you have Project1DE.exe Sisulizer will also import German translations from that file.

Java

If you add a Java resource file (.properties or .java) to a Sisulizer project, Project Wizard can import translations from localized resource files. For example if you have selected MyFile.properties file and there exists MyFile_de.properties file, Project Wizard will add German to the project and imports translations from MyFile_de.properties. Localized resource files must locate on the same directory as original one(s).

Qt

If you add a Qt file (.ts) to a Sisulizer project, Project Wizard can import translations from localized files. For example if you have selected MyFile_en.ts file and there exists MyFile_de.ts file, Project Wizard will add German to the project and imports translations from MyFile_de.ts. Localized files must locate on the same directory as original one(s).

XLIFF

Each XLIFF file is multilingual containg source and target language. If you add an XLIFF fiel to a Sisulizer projct Project Wizard can automatically add the target language to the project and can import translation from XLIFF file.

Importing from localized files

You can make Sisulizer to automatically import translations from output files. These files are the files that Sisulizer creates on build process. Notrmally there is not point to perform this because the project already contains same translations as the localized output files. However if you use some extenal file (such as Visual Studio) to edit the output file you can automatically import changes to your project. Choose Project | Import translations from localized files to import translations from localized files.

Importing manually

If you existing translations are on some other locations or files you have to manually import the translations by using File | Import or Column | Import menus.

Samples

The following table contains possible import sources and targets.

Source item File that Sisulizer project contains Example
*.<locale>.resx .NET resource file (.resx)
.NET project file (.csproj or .vbproj)
.NET solution file (.sln)
File in the project: MainForm.resx
Import file: MainForm.de.resx
<locale>\*.resources.dll .NET assembly file (.exe or .dll)
.NET project file (.csproj or .vbproj)
.NET solution file (.sln)
File in the project: MyApplication.dll
Import file: de\MyApplications.resources.dll
*<locale>.ext Visual C++ (.exe or .dll)
Delphi or C++Builder file (.exe or .dll)
File in the project: Project1.exe
Import file: Project1DE.exe
*<locale>.dll Visual C++ (.exe or .dll) File in the project: Project1.exe
Import file: Project1DE.dll
*.<locale> Delphi or C++Builder file (.exe or .dll) File in the project: Project1.exe
Import file: Project1.DE
*_<locale>.properties Java property resource file (.properties)  
*_<locale>.java Java list resource file (.java)  
*.<ext> Any file where the file format and file extension matches the import file. File in the project: Sample.xml
Import file: de\Sample.xml

The above examples always import German data from the import file to Sisulizer project.