Soluling Case: How We Localize Soluling
We localize Soluling with Soluling. Everything you see on this web site and in the product goes through the same process that we describe for our customers, so we know how it works in practice.
A hybrid method
We don't use only one tool. We use the hybrid method: the desktop application, the command line, and the cloud work together on the same projects.
- Soluling Desktop is where we create and maintain the projects: we scan the sources, set up the options, and check the result.
- The command line (SoluMake) scans the source files and builds the localized files without anyone clicking buttons.
- Soluling Cloud holds the projects, the translations, and the translation memory, so that everybody can translate and review in a browser.
What we localize
| What | Technology | How Soluling gets the strings |
|---|---|---|
Soluling Desktop application (Soluling.exe) |
Delphi Windows application | Soluling scans the application. It also scans the source code, which gives the translator the comments that we write after //loc. See the Delphi VCL guide. |
Soluling Desktop online help (Soluling.chm) |
Compiled HTML help | Soluling localizes the HTML topics of the help. |
| Soluling web pages (soluling.com) | ASP.NET Core | Soluling reads the strings from the localizer calls of the source code and creates the .resx files in real time, so we don't write them. It also scans the source code for the //loc comments. See the ASP.NET Core guide. |
| Soluling Translate application | Angular | Translate uses Angular's built-in localization method. Soluling scans the resource file that the Angular tools extract and creates the localized resource files. Translate uses Soluling's Angular library to change the language at run time. See the Angular guide. |
| Soluling backend database | SQL Server | Soluling reads the texts of the tables, such as the descriptions of the plans and the names of the features, and the web pages show the translation of the language of the visitor. See the database guide. |
Machine translation and post editing
We machine translate the strings with Soluling, and then post edit the machine translations. Today's machine translation engines are so good, especially when they use our own terminology as a glossary, that the machine translations hardly need any post editing.
Cloud and CI/CD
All the projects are in Soluling Cloud and connected to our CI/CD pipeline. Localization is a part of every build, not a separate project at the end of the release.
Try it yourself
Read the workflows to choose the combination that fits your team, and try Soluling with your own project.