Soluling home   Document home

Soluling Story

Several kinds of people use localization tools: developers, translators, managers, testers, and localization engineers. Each member of the team needs different features from the localization tool. For developers, the tool must understand the development tool such as Visual Studio, Android Studio, or Delphi. For example, a .NET developer wants to have a tool that is designed for .NET. Translators, on the other hand, do not care about development tools. They want glossaries, translation memories, import, and export features. Traditionally it has been challenging to combine features needed by translators and developers. Even developers of different platforms require different features.

There are many development tool specific localization tools. Typical for these is that they do reading and writing of that particular file format (e.g., Delphi form) very well but lack support for other platforms and do not contains features needed by translators. On the other hand, there are translator oriented tools that have all the features required by translators but having only a rudimentary file format support. There are also web-based tools that provide very easy access for the tool but lack many features needed by developers and translators.

Our goal was to make a reliable and high-performance tool that is ideal for both developers and translators. The main idea was to support all major file and database formats. This includes application files, document files, web files, data files, and databases. Supporting all these formats makes it possible that you can use a single tool for all your localization work. Many tools support several file formats, but if you look closer, you find that support for each format is very shallow. Our approach is different, and it means if we support a file format, we support it 100%. This means that Soluling can localize all elements of the file. You can translate everything. Not only strings and UI but all the data and custom resources such as image, audio, video, XML, JSON, text and even your proprietary binary data. There are no limitations or exceptions. If your original file follows the format set by the author of the file format, Soluling can fully localize it.

We have a few principals of how we implement file parsers, and we do not give them up:

• Scan all items. Even those that are inside proprietary binary data.
• If you don't give any translations, then the localized file should be 100% the same as the original. This includes white spaces, new lines, string separators, etc.
• Keep the string encoding the same if possible. If the original file is not Unicode, this cannot always be done, but a language-specific Ansi encoding must be used.
• Parse structured data such a way that translators can only see easy-to-translate strings and cannot by accident break the format.
• Present items as logical entities to the translator. Not as two ore more pieces when a translator can not see that they belong together.
• Scanning an unchanged file again must not make any changes to the Soluling project file.

If possible, we provide 100% native visual editor that looks as similar to your development tools editor. When not possible, Soluling offers an easy way to take and attach screenshots or quickly run a localized application on a viewer or an emulator.

• We implemented features needed by translators such as terminology, import, export, machine translation, and translation memory with fuzzy matching.
• We implemented teamwork features that make sending and receiving translation data as automatic and as safe as possible.
• We implemented crowdsourcing features that let you outsource the translation process for the users our your application.
• We put a price tag that doesn't scare you away. Soluling has many more features than its competitors but costs much less.

We started designing the tool in early 2010. We studied all major localization tools and services, adopted the ideas that we felt are useful and important. After that, there were several long years when our Delphi, C#, and TypeScript developers wrote the code, and our translators gave feedback. We got the main features done in late 2018. Starting 2018, the tool has been used in few companies as pilot projects to localize Delphi, WPF, Windows Forms, Angular, Android, XML, HTML, HTML Help, ASP.NET, and database projects. We opened a public beta in Q3 2019 and released in June 2020.

In 2026-2027 we will release Soluling cloud.

Soluling is our idea about a smooth, reliable, fast, and cost-effective way to localize your applications, documents, and data.

We hope you enjoy Soluling as much as we do.

Cheers,
Soluling team