Project Converter

Soluling home Document home

Soluling can convert most project files made in Sisulizer localization tool into the Soluling format. If you try to open such a project file, this dialog will be shown. Sisulizer used XML based project format that Soluling can read. For other localization tools but Sisulizer, there is no automatic conversion. 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 Sisulizer project to a Soluling project:

Open your project into Sisulizer tool.
Make Sisulizer to build localized files. Choose Project | Build All Sources in All Languages.
Close Sisulizer.
Start Soluling.
Click Open project and browse your Sisulizer project (.slp). You can also just drag and drop the project file on Soluling's main window.

Before the Project Convert dialog appears, Soluling reads the Sisulizer 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 Sisulizer project file. How the translations are imported depends on the selected Translation source value:

Translation source	Description
Project	Translations and their attributes are imported directly from the Sisulizer project file. This does not work with all source types (). If all translations do not exist in the converted project, select Localized files* or Both localized files and project files translation sources. * This conversion works currently on Delphi, ResX, Visual C++, INI, and XML sources.
Localized files	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 Sisulizer tool to create localized files before converting. Start Sisulizer, open your project, and choose Project \| Build All Sources in All Languages.
Both localized files and project files	Uses localized files first to import the existing translations and then the Sisulizer project file to import the attributes. This is the recommended method.

Translation source

Description

Project

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

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

Localized files

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 Sisulizer tool to create localized files before converting. Start Sisulizer, open your project, and choose Project | Build All Sources in All Languages.

Both localized files and project files

Uses localized files first to import the existing translations and then the Sisulizer project file to import the attributes. This is the recommended method.

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 correct source file context, but sometimes the calculated context does not match the real Soluling 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 or Both localized files and project files.

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 Sisulizer project file.

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 product wa an old and supported 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 your old localization tool is some other but Sisulizer, use your old localization tool to create localized files. Then use Soluling to create a new project containing the same file(s) to be localized. If the existing localized files are in the default location (e.g., language-specific subdirectories) or use the right naming convention, Soluling will find the existing localization files and import translations from them.