Selected Customers
Specials run until 11/20/2019
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.
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
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. [...]
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
Importing Data
Importing is very powerful feature of Sisulizer. It makes it possible to import existing translations from different sources to either Sisulizer project or translation memory. Sisulizer can import data from several sources:
- Importing existing translation when creating a new project
- Importing from existing localized files
- Importing project file of other localization tools
- Importing project sent by translator
- Importing from glossaries
- Importing from text and CSV files
- Importing to translation memory
- Importing tutorial
Importing existing translation when creating a new project
When you use Project Wizard to create a new project Sisulizer can automatically find existing translations and import them to the project. If Sisulizer finds existing translations it will show a message box during the Project Wizard asking if the user wants to import existing translations. If you click Yes Sisulizer imports the translations.
Read more about importing existing translations.
Importing from existing localized files
You can also import existing translations into existing project (e.g. after you have created the project). Use File | Import or Column | Import menus to start Import Wizard that lets you select the file you want to import.
Read more about importing existing translations
Importing project file of other localization tools
Sisulizer can directly open project files of other localization tools. When you open such a file (File | Open) Sisulizer first creates a new Sisulizer project file that contains the same source file and then imports data from localized files created by you previous localization tool or from project file of you previous localization tool.
Importing project sent by translator
When you get a translation project (.slp) back from translator you can easily import the new translations to the project by choosing File | Exchange, File | Import or Column | Import menus.
Importing from glossaries
You can import data from glossaries such as TMX, text, Excel files or from database tables. Choose File | Import or Column | Import to start Import Wizard. Sisulizer can import data from following file formats and databases.
| File format | Description |
|---|---|
| Borland Translation Repository file | Imports data from a Borland Translation Repository file. Use this if you want to import data from ITE's translation storage (.xml). |
| Comma Separated Value file | Imports data from a CSV file (.csv). Note! This has the same file extension as Microsoft Glossary files but the format is different. Read more about importing text and CSV files. |
| Database table | Imports data from a database table. |
| EDICT dictionary file | Imports data from an EDICT file. The file contains Japanese-English dictionary. |
| Excel file | Imports data from a selected range from Excel sheet (.xls). |
Microsoft glossary file |
Imports data from a Microsoft Glossary file (.csv). Note! This has the same file extension as Comma Separated Value files but the format is different. Read more about importing text and CSV files. |
| Multilizer dictionary file | Imports data from a Multilizer binary dictionary file (.mld). |
| Multilizer project file | Imports data from a Multilizer project file (.mpr or .m7p). |
| PO file pair | Imports data from a PO file (.po). |
| Regular expression defined text file | Imports data from a text file containing several columns. Note! Some text files are called as Command Separated Value files and uses .csv file extension but do not have the same file format as Microsoft CSV files. Import those kind of files as Regular expression defined text files instead of Comma Separated Value files. Read more about importing text and CSV files. |
| Resx file pair | Imports data from a .NET resource file (.resx). |
| TBX file | Imports data from a TBX file |
| TMX file | Imports data from a TMX file |
| XLIFF file | Imports data from a XLIFF file |
Note! Depending on your Sisulizer license some of the above formats might be disabled.
Importing to translation memory
You can import translations to the translation memory by choosing Tools | Translations Engines. Translation Engines dialog shows up. Select the translation memory where you want to import to. Select Documents sheet and click + button to start Import Wizard.