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
Windows dialog, forms and menus uses hotkey characters. They are marked with & character. For example &File contains an F hotkey. F&ile contains I hotkey. It is recommended all items in the same form, dialog or menu have an unique hotkey. Sisulizer can automatically insert and check out hotkeys.
Asian languages use ideographs instead of alphabets. This is why these languages generally uses a bit different approach to mark hotkeys. They add a single alphabet inside parenthesis in the end of the string.
&File -> ファイル(&F)
Sisulizer can properly handle Asian hotkeys with Chinese, Korean, Japanese and Thail languages.
Sisulizer contains hotkey validations. They can be applies both to the original and translated files.
When applying to the original files you can check that your original file do not contain duplicate hotkeys. If they do you can fix them before you start localization work.
When applying to the localized files you can check that you translations are right. There are not missing, extra, invalid or duplicate hotkeys. In most cases Sisulizer can automatically fix them.
By default Sisulizer's translation memory removes all special characters including hotkey from the translation before adding them to the translation memory. When applying translation memory using automatic translation Sisulizer automatically adds a hotkey if the original string contains hotkey.
For example if we have &File string in our project and its Japanese translation is ファイル(&F) Sisulizer adds [File -> ファイル] translation pair to the translation memory. When using the translation memory for File string Sisulizer translates it to ファイル. When using the translation memory for &File string Sisulizer translates it to ファイル(&F). When using the translation memory for F&ile string Sisulizer translates it to ファイル(&I).