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 370 released
1/3/2018
The new build comes with many new features. [...]
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 [...]
Delphi 10, VS 2015, .NET 4.6
10/14/2015
Up-to-date for the future. [...]
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
Localization Service Providers use Sisulizer to create multiple versions of PC and mobile software for their customers. The globalization of the software industry makes it cost-effective to create separate versions of applications for several languages. And LSPs rely on Sisulizer to manage their localization and translation work.
Some localization services use the Development version of Sisulizer to manage projects for multiple clients. Other localization providers use the Free of Translator edition and work with software publishers and owners who themselves have purchased a Development license.
Sisulizer makes it easy to manage software for their clients' localization projects. Sisulizer's straightforward management process ensures that LSPs and software owners work together effectively.
Each localization project within the mechanical engineering company is a three-step process.
First, the software developer or localization manager uses Sisulizer to scan the software application and locate all of the text. Sisulizer runs on Windows, and works directly with popular development platforms like .Net, C++Builder, Delphi, FireMonkey, Visual Basic, Visual C++, Java, Windows binary files, and other.
The program works visually with HTML and XML. Sisulizer can also grab text from files widely used to store translatable content like .txt, .ini, or .po, JSON files and databases.
The software owner determines which Windows resources to translate and localize, including icons, menus, dialog boxes, strings, accelerators, versions, and manifest resources.
Software developers like Sisulizer because it also operates in the mobile world. The software supports Android, and J2ME, .NET for Smart Devices, and Windows Mobile.
Alternatively, a trusted, experienced localization service provider can perform Step One for the software owner, as well as the following two steps.
Second, the LSP's translators use Sisulizer's visual editor to do the translation work. They begin the translation work, and mark each phrase as translated properly, auto-translated, translated by best guess, out for review, or complete. Alternatively, the mechanical manufacturer's IT staff can use Sisulizer's Exchange Wizard to create and send an outside translator a single file that contains a self-installing Sisulizer Free Edition, along with the project file.
When the LSP's translators or freelancers have completed their translation work, they'll run Sisulizer's Exchange Wizard to create a single file that is sent back to the mechanical manufacturing firm. The translator never has access to your source code, so there is never a risk that you will lose control of confidential information, such as hardware trade secrets. And there is no risk that the translator will accidentally change the source code and adversely affect the operation - or the safety features - of the automation equipment.
The translator never has access to your source code, so there is never a risk that you will lose control of confidential information such as hardware trade secrets. And there is no risk that the translator will accidentally change the source code and adversely affect the operation of the device.
Third, the software owner's company's IT department will build the new localized version of the software. Simply run Sisulizer using the translated file, and build the new version of the software application in the new language. There's no need for the mechanical manufacturer's IT staff to manually track where each text snippet belongs. Sisulizer manages the localization project, and automatically builds the new version of the application that controls your mechanical hardware device.
In support of localization service providers large and small, Sisulizer easily handles all languages, including right-to-left and double-byte languages. The program keeps track of what has already been translated, making it fast and inexpensive for you to translate later versions of the software application.