Soluling home   Document home

Project Converter

Soluling can convert some project files made in other localization tools into the Soluling format. If you try to open such a project file, this dialog will be shown. The formats that can be automatically converted are Sisulizer and Multilizer. They both use XML based project format that Soluling can read.For other localization tools but Sisulizer and Multilizer, automatic conversion is impossible. However, if you have the existing localized files in standard locations, then Soluling will find them and automatically import the translations after you have added the original file into your Soluling project.

Follow these instructions to convert your existing project to a Soluling project:

  1. Open your project into your previous tool (Sisulizer or Multilizer).
  2. Make the tool to build localized files. In Sisulizer, choose Project | Build All Sources in All Languages. In Multilizer, choose Project | Build All.
  3. Close your previous tool.
  4. Start Soluling.
  5. Click Open project and browse your project (.slp, .mpr, or .m7p). You can also just drag and drop the project file on Soluling's main window.

Before the Project Convert dialog appears, Soluling reads the old project file and populates Languages, and Sources list boxes of the dialog. Once the dialog appears, uncheck any source or language that you don't want to import. When converting, Soluling creates a matching Soluling project and reads the properties from the existing project file. How the translations are imported depends on the selected Translation source value:

Translation source Sisulizer Multilizer Description
Project yes no

Translations and their attributes are imported directly from the old project file. This is the recommended method, but this does not work with all source types (*). If all translations do not exist in the converted project, select Localized files or Both translation sources.

* This conversion works currently on Delphi, ResX, INI, and XML sources.

Localized files yes yes

Translations are imported from localized files. This works with all source types. Translation attributes, such as status, are not converted.

If your localized files are not up to date, it may be that they do not contain the most recent translations that are in your current project file. This is why you must use your old localization tool to create localized files before converting. The following table contains instructions on how to create localized files in various localization tools:

Sisulizer Start Sisulizer, open your project, and choose Project | Build All Sources in All Languages
Multilizer Start Multilizer, open your project, and choose Project | Build All
Both localized files and project files yes yes Uses localized files first and then the project file.

Check Create an optimized project file that contains only strings and stores only necessary data if you want to create an optimized project that does not contain user interface layout information and images.

Check Import also strings that equal to the original strings if you want to import also translations that are the same as the original strings.

Check Use value only matching if you want to accept values where the original value (not also the context) matches. Soluling tries to calculate the collect context of the import format, but sometimes the calculated context does not match the real context, and the import does not happen. In that case, make sure you import from localized files or check this.

Check Import translation properties from the project file if you want to import the attributes (e.g., status) of the translations as well. Visible only if the translation source is Project.

Click Start when you want to start the conversion project. As a result, your new Soluling project contains the same sources, translations, and properties as your old project file.

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

Note! Not all Sisulizer and Multilizer projects can be converted. Both products are very old and support legacy formats such as Classic Visual Basic, Symbian, and Palm OS. Soluling does not support these legacy formats because those formats are just not used anymore. If your project file contains such a legacy file, the conversion process just skips that file.

Note! If the conversion does not work, use your old localization tool to create localized files. Then use Soluling to create a new project. Suppose the existing localized files are in the default location (e.g., language-specific subdirectories) or use the right naming convention. In that case, Soluling will find the existing localization files and import translations from them.