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


MFC's resource DLLs

MFC 7 and later has a build in feature using resource DLLs. When a MFC applications starts MFC is looking for a possible resource DLL from the same directory where the original .exe or .dll is located. If MFC can find this it uses resources of the resource DLL instead of the original PE file. Resource DLLs are named ApplicationNameXXX.dll, where ApplicationName is the name of the .exe or .dll using MFC, and XXX is the three-letter code for the language of the resources. For example MyApplicationENU.dll is an English (United States) DLL and MyApplicationDEU.dd is German (Germany) DLL.

How to create resource DLLs

To make Sisulizer to create localized resource DLLs for your MFC file right click the source name on the project tree and choose Properties. Check Resource DLL files check box.

Initial language

MFC attempts to load the resource DLL for each of the following languages in order, stopping when it finds one:

  1. The current user's default UI language, as returned from the GetUserDefaultUILanguage() Win32 API. (Windows 2000 or later only)
  2. The current user's default UI language, without any specific sublanguage (that is, ENC [Canadian English] becomes ENU [U.S. English]). (Windows 2000 or later only)
  3. The system's default UI language. On Windows 2000 or higher, this is returned from the GetSystemDefaultUILanguage() API. On other platforms, this is the language of the OS itself.
  4. The system's default UI language, without any specific sublanguage.
  5. A "fake" language with the 3-letter code LOC.

If MFC does not find any satellite DLLs, it uses whatever resources are contained in the application itself.

As an example, suppose that an application MyApplication.exe uses MFC and is running on a Windows XP. The system UI language is ENU [English (United States)] and the current user's UI language is set to DES [German (Switzerland)]. MFC will look for the following DLLs in the following order:

  1. MyApplicationDES.dll (user's UI language).
  2. MyApplicationDEU.dll (user's UI language without the sublanguage, in this example German (Germany).
  3. MyApplicationENU.dll (system's UI language).
  4. MyApplicationLOC.dll.

If none of these DLLs are found, MFC will just use the resources in MyApplication.exe

Runtime language change

It is not practical to implement runtime language change in MFC. It is possible but not without significant need to modify your existing code.