Learning Blazor

Chapter 5. Localizing The App

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the fifth chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

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 user experience 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?