Q&A
Answers to the questions we hear most often about Soluling - what it is, how the desktop and cloud tools relate to each other, what happens to your source code, and how Cloud billing works. For the full picture, see the Desktop and Cloud documentation.
General
Three things in particular.
First, Soluling supports two ways of working. In one, like most other localization platforms, you push your files to the cloud, they're translated there, and you pull the localized files back to use them. In the other, you use SoluMake to scan and build locally, and only the strings and their metadata are pushed to the cloud - your files themselves never leave your infrastructure.
Second, Soluling supports 100+ file and database formats, including complex ones most cloud localization platforms don't touch at all, such as compiled EXEs and DLLs, Visual Studio projects, and databases - not just simple text-based formats like JSON and XML.
Third, Desktop and Cloud aren't separate products bolted together - they're the same platform, so you can scan and build locally with Desktop or SoluMake while translators work in the Cloud web app, moving between the two as a project needs rather than being locked into one or the other.
Formats and projects
.ntp). Push that file to the cloud so translators can work on it there; once translation is done, pull the translated project file back down and build it locally - on your development machine, a build server, or a CI/CD pipeline. Your source code and compiled binaries themselves never have to leave your own infrastructure.
.sln/.slnx) and projects (.csproj/.vbproj) directly and understands the software project structure inside them, so you don't have to hunt down and select individual resource files by hand.
Translation quality
//loc comment, a .resx comment, or an ARB description), its maximum length, and the glossary terms in it. That is the same information a human translator sees, so the AI can tell "Open" the command from "Open" the status. Such translations are listed first in the suggestions, both in Soluling Desktop and in the browser. Add comments to short and ambiguous strings to get the best results. For instructions that apply to the whole project, such as the tone or words that are never translated, write a style guide. See context-aware AI translation.
In Soluling Cloud, machine translation uses the terminology too. Soluling imports the account's terminology as a glossary to compatible machine translation engines, so they translate the terms the way you have translated them. The glossaries are updated automatically whenever the terminology changes. The desktop application can use DeepL and Amazon Translate glossaries that you create in their configuration dialogs.
Automation and integration
.ntp project file - it scans, machine-translates, and builds there, and only the extracted strings and their translations ever reach Soluling's servers. SoluCLI instead talks only to the REST API - it doesn't scan or build anything itself, it pushes files up and lets the cloud do that work, then pulls the results back down. Pick SoluMake to keep source files off the cloud entirely on a Windows build agent; pick SoluCLI when you're fine with the cloud doing the work, or your build agent runs Linux or macOS, where SoluMake isn't an option.
POST /users/authenticate and renew with POST /users/refresh. Once signed in, the API covers project management, terminology, translation memory, spell checking, machine translation, project invitations, and licensing - see the full API reference, generated directly from the API so it's always up to date.
Security and your source code
Soluling Cloud
Pricing and billing
Didn't find your answer here? Contact support.