Chapter 5. Localizing the App
In this chapter, I’m going to show you how to localize Blazor WebAssembly apps. Using the Learning Blazor App as an example, I’ll show you how an app can be automatically localized into dozens of languages. You’ll see how Blazor WebAssembly recognizes static resource files for the client browser’s corresponding language. You will also learn how to consume the framework-provided IStringLocalizer<T> interface type. Additionally, I’ll show you one possible way to machine translate static files at rest with a GitHub Action using the Azure Cognitive Services Translator.
We live in a global society, and an application that speaks to one group of people is a disappointment. Not only will this dramatically affect the UX for those who do not speak the app’s language, but if the app contributes to an online shopping experience, for example, it will have a detrimental effect on sales as well. This is where localization comes in.
What Is Localization?
Localization is the act of translating static resources, such as those found in resource files, into a specific language that an app plans to support. When your app supports many languages, it will have various resource files for each supported locale. In .NET, localization maintains locale-specific resource files in an XML format with the .resx file extension.
Note
Localization is not the same thing as globalization. Globalization is when you code your app in a way that makes it easy to localize. For an overview ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access