Languages & cultures explained
If you build an application using the AuthP library, then by default any of the messages and errors from the AuthP services will be in generic English. But since AuthP version 4.1.0 you can can either:
- Change the messages / errors coming from the internal code into another language.
- Or if your application is used in multiple countries you can support many languages.
.NET refers to supporting many languages as localization and alongside localization is globalization, which is about input and displaying data in the right format (e.g. date formats). Both the localization and globalization are controlled by the culture of the user or application, for instance the culture with a Name of "en-US" is American English with the "Color" spelling and a date format of "month/day/year". See this Microsoft document about all these concepts.
Version 4.1.0 of AuthP library has a built-in localization system, which is turned off by default. This means you can use the AuthP library using English without having to set up the .NET localization services, which isn't a quick thing to set up. But if you want replace the English messages with a different language or support many languages in your application, then you need to:
- Setup the .NET localize service - See [???]
- Setup resource files for the extra languages - See [???]
- Register the AuthP localization - See [???]
To make this work I had built a library, called Net.LocalizeMessagesAndErrors, that didn't need a developer to set up .NET localization services even if they only wanted English messages. And I have altered the Example1 ASP.NET Core app to support both the normal English and a French version of the AuthP's services, plus some of the frontend to show English or French depending on the set culture. The figure below shows the same view in English and French, especially note that the red error message came from the AuthP's Roles admin code.
- [How to turn on the AuthP's localization service]
- [Usages -> Supporting multiple languages]