Localization guides for the platforms you build
Each guide takes a sample application from English-only to localized, step by step: where the platform keeps its texts, what you prepare in the code, what Soluling reads and builds, how the application loads its language, and how you keep the translations current.
Try Soluling See supported formats
Where to start
Choose the guide by the framework your application is built with and by what you deploy.
| Guide | Start here when | Typical input | Localized output |
|---|---|---|---|
| .NET Windows Forms | Your .NET application has forms with Localizable set, and you want to translate them visually. |
.csproj, .vbproj, .slnx, .sln, .exe, .dll, .resx |
Satellite assemblies (fi\App.resources.dll) or localized assemblies |
| .NET WPF | Your .NET application uses XAML windows and pages, with or without .resx strings. |
.csproj, .vbproj, .slnx, .sln, .exe, .dll, .xaml, .resx |
Satellite assemblies with localized XAML, or localized assemblies |
| WinUI | Your Windows App SDK application uses WinUI 3 XAML and .resw string resources, in C# or C++. |
.csproj, .vbproj, .slnx, .sln, .xaml, .resw, images and other files |
Localized resources in language folders (fi\Resources.resw) built into one application |
| Visual C++ | Your native Windows application uses standard Windows resources: dialogs, menus, and string tables. | .exe, .dll, .rc |
Localized executables (fi\App.exe) or MFC resource DLLs (AppFIN.dll) |
| Delphi VCL | You build Windows applications with Delphi or C++Builder VCL and want to localize the compiled file. | .exe, .dll, .bpl with .drc |
Localized executables (fi\App.exe), resource DLLs (App.fi), multilingual or embedded files |
| Qt | Your Qt application marks its strings with tr or qsTr. |
.pro or the .ts file from lupdate |
Localized .ts files (strings_fi.ts) and compiled .qm files |
| Databases | Your tables hold text or images that the user sees, such as product names and descriptions. | A database file (.accdb, .db) or a connection to a database server |
Localized database files (fi\Sport.db), or translations written to rows, fields, or tables |
| Android | Your Android application keeps its strings in strings.xml, or you also want to localize layouts and images. |
res\values\strings.xml or the Android Studio project (.iml) |
Localized resources (res\values-fi\strings.xml) that Android Studio builds into one application |
| .NET MAUI | Your .NET MAUI application keeps its strings in .resx files and uses them from XAML with x:Static. |
.csproj or the .resx files themselves |
Localized .resx files (AppResources.fi.resx) that the .NET build compiles for every platform |
| ASP.NET Core and Blazor | Your web application uses IViewLocalizer or IStringLocalizer, and you don't want to maintain the original .resx files. |
.csproj, .slnx, .sln with localizer strings in .cshtml, .razor, and .cs files |
Localized .resx files and satellite assemblies (fi\App.resources.dll) |
| Angular | Your web application uses Angular's i18n attributes and $localize. |
messages.xlf, .xmb, .arb, .json from ng extract-i18n |
Localized resource files (messages.fi.xlf) for ng build --localize |
| React | Your React application uses React Intl, with FormattedMessage and formatMessage. |
en.json from formatjs extract |
Localized runtime files (fi.json) that the application imports |
| gettext and PO | Your application marks its strings with gettext or _. |
.pot or .po from xgettext |
Localized .po files and compiled .mo files |
| Delphi FireMonkey | Your FireMonkey application runs on Windows, macOS, iOS, Android, or Linux. | .dproj with the compiled application and .drc |
A multilingual resource file (NtLangRes.ntres) or language files (fi.ntlang) |
Choose by how the application stores its user interface
Windows Forms
Forms with Localizable set keep their texts, sizes, and positions in .resx files. Translate them in the visual form editor and build satellite assemblies.
WPF
Windows and pages are XAML. Soluling localizes the XAML and the .resx strings together. Add an x:Uid when you localize the compiled assembly or switch the language at runtime.
Only .resx strings
If your .NET application keeps only strings in .resx files, localize the files themselves, in Soluling Desktop or directly in Soluling Cloud.
Delphi VCL
Forms and resource strings are resources of the compiled Windows file. Soluling builds localized copies or resource DLLs, without the source code.
Delphi VCL guide →Visual C++
Dialogs, menus, and string tables are standard Windows resources. Soluling replaces them in a copy of the executable, or builds the resource DLLs that MFC loads.
Visual C++ guide →Delphi FireMonkey
Mobile platforms don't support resource DLLs, so FireMonkey applications carry every language in one resource file that Soluling builds and Soluling's library reads.
Delphi FireMonkey guide →Every guide answers the same questions
Where do the texts live?
Forms, XAML, resource strings, string tables, or extracted resource files, and what stays hard-coded in the code.
What do developers prepare first?
Moving strings to resources, whole sentences with placeholders, plural patterns, and stable identifiers.
What is built, and how is it loaded?
The localized files Soluling builds, how the application chooses its language, and whether it can change it at runtime.
How do updates work?
Scanning a new build, keeping the existing translations, and translating only what changed, also in a build pipeline.
On your desktop or in the cloud
Every guide works with
Soluling Desktop
and SoluMake, and has a section on
Soluling Cloud, where translators work in a browser. Resource files such as .resx, .xaml, .rc, and Angular's messages.xlf can be uploaded to the cloud directly; compiled applications are scanned in Soluling Desktop and uploaded as a project, so they never leave your machine.
Also supported
There's no guide for these platforms and formats yet, but Soluling localizes them too. Each link goes to its Desktop documentation; see supported formats for the full list of more than 100 formats.
Try it with your own application
Download Soluling or try Soluling Cloud, and follow the guide of your platform or start with its sample.
Try Soluling See supported formats