Localizing a WPF application is not an easy task. Almost any article on the localization of WPF is replete with details and manual steps to implementation of a localized application.
Localization using the utility LocBaml as described by Microsoft has lots of advantages, but is difficult to maintain. André van heerwaarde in his article proposed to simplify this decision by using the configured build step. He wrote a utility to merge the translated text fragments. However, in his article, there are still many manual steps.
Visual Studio Project Template
I propose to use a Localized WPF Application template I've created to start working on a multilingual WPF application. Projects created using this template already contain all the necessary tools for localization, as well as automates the localization process.
During application development, you add a new XAML file without having to worry about localization. Upon completion of the changes, simply build the project.
- The custom build step will call msbuild / t: updateuid [Project Name].csproj. This step will automatically add
x:Uid at every element containing the text elements.
- Then the build process will automatically start LocBaml, which finds all the text elements in the XAML file and generates a CSV file containing the text elements.
- The next step will run the utility from
MergeLocBamlCsv by André van heerwaarde. As a result, the earlier translated segments will be merged with the new ones.
- The utility
StripLocBamlCsv cuts unused items from the CSV file.
The only thing you have to do manually is to add new languages and the actual translation itself.
Adding a New Language
To add a new language in the draft, you will have to:
copy Translation\Translate.csv Translation\Translate.ru-RU.csv
add a new language, for example:
- Copy the location of the neutral language in the new CSV file
- Open the project file in a text editor, and after these lines:
Then you need to reopen the project in Visual Studio. If the project was already open, the IDE will ask whether you wish to reopen the project to reflect the changes, answer 'Yes'.
If you did not make mistakes, then the newly opened project folder Translation will have a new file Translate.ru-RU.csv.
Start the assembly to update the translation files, then you can open a new file and start translating.
Localize Text in code-behind
StringResources.xaml is a Resource Dictionary example for translated
The usage is as easy as:
this.Title = (string)FindResource("MainWindow");
Links and Credits
I'm Android and Full Stack Software Engineer. 28 years in software industry, lots of finished projects. I’m never afraid of learning something new and you can see it by amount of skills in my resume.
I'm working remotely since 2009, self-motivated and self-organized.
There are no impossible projects. I have experience with Android, iOS, Web, Desktop, Embedded applications, VR, AR, XR, Computer vision, Neural networks, Games, IoT, you name it.