
Soluling is a localization tool and service that contains all the features you need to localize your projects, and it makes localization easy. Soluling supports 100+ file formats. With Soluling, you can localize software: desktop applications, mobile applications, and web applications. You can also localize documents and online help, data files, and databases.
You can use Soluling in several ways:
First, read the Soluling Desktop tutorial or the Cloud tutorial.
When you want to localize something, you usually have an original file or database. You want the localized files and databases to have the same structure as the original ones, with the strings and other localizable items translated into the target language. Soluling works on this principle.
When Soluling scans the original files, it extracts all the information needed to safely put the translations back, even if the original files change during the translation. This makes continuous localization easy. Soluling decouples the localizable strings from the original files, so developers and translators can work independently of each other. You choose where the scanning and building happen:
The following steps show how to use Soluling.
![]() |
1. Create and scan the project |
Select a source file or database you want to localize. Soluling reads the file or database, extracts the items to be localized, and saves them into a Soluling project file (.ntp).
In Soluling Desktop, choose File | New | New from File or Files or click New from File or Files on the start view to select a file. To select a database, choose File | New | New from SQL Database or click New from SQL Database on the start view. They all start Project Wizard, which lets you select the file or database and set its properties. When you complete the wizard, Soluling creates a new project that contains the selected items. The top-level items of a project are called sources. Each source is a file, a file pattern, or a database that you want to localize. To add a new source to an existing project, open the project and choose Home | Project | Project | Add File Source or Home | Project | Project | Add Database Source. Both start Source Wizard, which lets you select the file or database to add. Soluling also contains many other useful wizards.
In Soluling Cloud, click Add a new project on the dashboard and upload the file, or create the project in Soluling Desktop and click Translate | Configure Cloud to upload it. The page of each file format describes the Cloud process of the format.
After you add items to the project, Soluling scans them and extracts the elements that need to be translated. If you later modify the original file, rescan the project: choose Home | Project | Scan. Soluling reads all the items of the project again. If the items contain new or changed elements, Soluling adds or changes them in the project. No existing translations are lost. The new and changed elements are marked, so you can easily see what has changed.
If you already have localized files when you start using Soluling, that is no problem. When you add a new item to the project, Soluling looks for existing localized files. If it finds any, Project Wizard asks whether you want to import the translations from them. This makes it easy to reuse existing translations. If Soluling cannot find the localized files automatically, you can import them manually by choosing File | Import.
If your source code files are not properly internationalized, you can use Resourcer, the resource command of SoluMake, to replace hardcoded strings with resource strings. Resourcer is in beta.
See the full list of supported file formats and databases.
![]() |
2. Translate |
Once you have added the items you want to localize, it is time to translate them. You have several ways to translate. You can type translations in the translation grid and editors of Soluling Desktop or in Translate in your browser. You can use translation memory to reuse earlier translations, terminology to translate terms consistently, and machine translation to translate items automatically. You can also import existing translations from various sources.
If somebody else will do the translation job, you can send the project file to your translator to be translated. Usually, you use one translator per language, but if your project is very large, you can use several translators for one language. In that case, the project is split between translators, and several translators can work on the same project simultaneously.
With Soluling Cloud, you do not have to send files. Invite a translator for each language on the project's Manage page, and the translators work in Translate.
Soluling contains several features that make your translations more accurate: artificial intelligence, spell checking, terminology, validation, and pseudo translation. The spell checker detects misspelled words and incorrect grammar. Terminology helps you use consistent translations. Validation detects translations that are missing some required data or that do not fit their context. Pseudo translation makes it easy to test your application with various translations and scripts.
The translation grid lets you view and change any translation quickly and easily. The grid works like an Excel sheet. It shows the original and translated values of each row plus additional information, such as comments and statuses. You can use filters to show only certain types of elements.
In addition to the translation grid, Soluling Desktop shows a visual editor if the selected element is a visual element, such as a dialog or a form. The visual editor shows the element in the same way as your development tool (e.g., Visual Studio or Delphi). Soluling's visual editors are native: what you see in the editor is what you see when you run the application. In the editor, you can move and resize the components of the form.
In most cases, you only have to translate the strings. However, Soluling lets you localize other kinds of data too: location, size, font, color, images, audio, videos, XML data, etc. If an element is in the resource data, Soluling can localize it, even if it contains your own proprietary binary data.
![]() |
3. Build and test |
After you have translated the project, it is time to build the localized files or databases. In Soluling Desktop, choose Home | Project | Build All. Build creates the localized files of the active language, and Build All creates the files of all the languages of the project. Choose Home | Source | Run to run or view a localized file quickly. If you use Soluling Cloud, import the translations with Translate | Import from Cloud before you build, or build the localized files on the project's Manage page in Soluling Cloud and download them.
If you use continuous localization, build the localized files on your build server when you build your application.
Before you deploy your localized application and files, they need to pass localization testing.
![]() |
4. Rescan and go back to the Translate step |
After you modify your original files, let Soluling scan your files or databases again. In Soluling Desktop, choose Home | Project | Scan, and if you use Soluling Cloud, click Upload to Cloud. If you uploaded the file to Soluling Cloud directly, click the project's Update file button on the dashboard. If Soluling finds new or changed strings, perform steps 2 and 3 again. You keep going like this for the whole lifecycle of your application.
You can automate the whole process with SoluMake. It is a powerful tool that you can use in your make or build automation tool. It can scan, import, export, machine translate, and build, and it can upload projects to Soluling Cloud and download the translations. Only the manual translation work cannot be done on the command line. Your translators use Soluling Desktop or Translate.