Soluling home   Document home

Converting from Another Localization Tool

Soluling can convert most project files made with the Sisulizer or Multilizer localization tools into the Soluling format, because both tools use an XML-based project format that Soluling can read. Other localization tools have no automatic conversion. However, if the existing localized files are in their standard locations, Soluling finds them and imports the translations after you have added the original file to your Soluling project. You can also import the translations that the other tool exports in TMX or XLIFF.

• Converting from Sisulizer
• Converting from Multilizer
• Converting from other tools
• Using the converted project in Soluling Cloud

Converting from Sisulizer

Sisulizer works on the same principle as Soluling: it creates the standard resource formats and files of each framework or platform. This makes the conversion straightforward. To convert your Sisulizer project to a Soluling project:

1. Open your project in Sisulizer.
2. Build the localized files: choose Project | Build All Sources in All Languages.
3. Close Sisulizer.
4. Start Soluling.
5. Click Open and select your Sisulizer project file (.slp), or drag and drop the project file on Soluling's main window.

The dialog lets you set the conversion options, such as whether to import also the translations that equal the original strings, whether to match by value only, and whether to import the translation properties from the project file. Uncheck the sources and languages that you do not want to import. Soluling creates a matching Soluling project and reads the properties of the Sisulizer project file. How the translations are imported depends on the Translation source:

If your Delphi application used Sisulizer's Delphi library for a runtime language switch:

1. Remove the Sisulizer units and functions from your code.
2. Add Soluling's counterparts, which work similarly. Learn more about the runtime language switch.

Note! Conversion may not be 100%. There might be some properties or resource types that do not convert.

Note! Not all Sisulizer projects can be converted. Sisulizer supported legacy formats, such as Classic Visual Basic and Symbian, which Soluling does not support because they are no longer used. If your project contains such a file, the conversion skips it.

Converting from Multilizer

In most cases, Multilizer works on the same principle as Soluling: it creates the standard resource formats and files of each framework or platform. This makes the conversion straightforward. To convert your Multilizer project to a Soluling project:

1. Open your project in Multilizer.
2. Build the localized files: choose Project | Build All.
3. Close Multilizer.
4. Start Soluling.
5. Click Open and select your Multilizer project file (.mpr or .m7p), or drag and drop the project file on Soluling's main window.

The dialog lets you set the conversion options. Uncheck the sources and languages that you do not want to import. Soluling creates a matching Soluling project and reads the properties of the Multilizer project file. How the translations are imported depends on the Translation source:

Note! Conversion may not be 100%. There might be some properties or resource types that do not convert.

Note! Not all Multilizer projects can be converted. Multilizer supported legacy formats, such as Classic Visual Basic, Symbian, and Palm OS, which Soluling does not support because they are no longer used. If your project contains such a file, the conversion skips it.

Multilizer VCL components

If your Delphi application uses Multilizer's localization components, you have to do a bit more work. First, convert the project as described above. Soluling creates a new project and imports your existing translations from your Multilizer project file (.m7p).

Multilizer and Soluling work differently. Your Multilizer project refers to your Delphi project file (.dpr). When scanning, Multilizer reads the form files (.dfm) and source code files (.pas), and when building, it creates a Multilizer dictionary file (.mld). Your forms contain Multilizer components, such as TIvTranslator and TIvBinaryDictionary, that make them multilingual.

Soluling follows the standard internationalization method of VCL. You do not need any localization components, but you use resource strings. When the Delphi compiler compiles your application, it stores the form data and the resource strings as standard Windows resources inside the .exe, .dll, or .bpl file. Soluling scans this file and extracts the form and string resources. When building, Soluling creates a resource DLL for each language, which you deploy with your application. VCL has built-in code that uses the resources of the matching resource DLL instead of the .exe file. If you want a single-file deployment (only the .exe), Soluling can embed the resource DLLs in your original .exe file as custom resources that the application extracts the first time it starts. If you want a runtime language switch, use Soluling's Delphi library.

Because of these differences, you need to refactor your code:

1. Remove all Multilizer components (TIvTranslator and TIvBinaryDictionary) from your forms.
2. Remove all Multilizer units and functions (e.g., Translate) from your code.
3. Use Delphi's standard resource strings instead of Multilizer's Translate function.
4. Add Soluling's runtime language switch code if you need it. Unlike Multilizer, it does not need a translator component on each form.

Converting from other tools

If you used another localization tool, there are two ways to reuse its translations:

• Localized files. Use your old tool to create the localized files. Then create a new Soluling project that contains the same original files. If the localized files are in the default locations (e.g., language-specific subdirectories) or use the right naming convention, Soluling finds them and imports their translations.
• TMX or XLIFF. Most localization tools and services can export their translations as TMX or XLIFF files. Import the file into your Soluling project or into your translation memory. This works even if the localized files are not in their standard locations.

Using the converted project in Soluling Cloud

The converted project is a normal Soluling project file (.ntp). To translate it in Soluling Cloud, open it in Soluling Desktop and choose Translate | Configure Cloud to upload it. Your translators can then translate it in their browsers in Translate.