How to handle localized content in ASP.NET Core?

Question

what is the best way to store and display localized user-supplied content through models in ASP.Net Core so that your site can be multilingual? The ASP.NET localization guides show how to localize the static parts of a web site like labels and messages.

I'm looking for a way to be able to store localized user-supplied content in multiple languages, and display the correct language based on in the user's selection. So if the language is set to Thai, the application displays the Thai versions of the content, such as product description in Thai.

Is there a way to do this in ASP.NET Core?

nopCommerce provides this feature - you can add multiple languages and enter details for product, user, category models etc in all the languages that you've selected (see image).

nopCommerce bilingual model entry form

nopCommerce stores these localization features in a database table (LocalizedProperty) essentially as key-value pairs with foreign keys to determine the object it's tied to.

nopCommerce LocalizedProperty table

How do you make the application serve the correct values from such a table depending on locale?

Does this answer your question? [ASP.NET Core DisplayAttribute Localization](https://stackoverflow.com/questions/37833661/asp-net-core-displayattribute-localization) — Panagiotis Kanavos, Oct 07 '20 at 12:52
Not exactly. I want to be able to store all fields in a model (e.g. Product) in as many languages as are necessary, so that when the user changes the language, the fields from the model are displayed in the correct language. — KiwiNFLFan, Oct 07 '20 at 20:17
You can do that by creating resources for multiple languages. ASP.NET Core will pick the correct one based on the user's preferred language — Panagiotis Kanavos, Oct 07 '20 at 20:59
BTW the translated resources don't have to come from an embedded resource file, they can come from other sources, eg: satellite (language-specific) assemblies, JSON files or database tables, [anything that implements the correct interface](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/localization-extensibility?view=aspnetcore-3.1). These [example projects](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/localization-extensibility?view=aspnetcore-3.1#localization-resources) load resources from JSON or [a database](https://github.com/damienbod/AspNetCoreLocalization) — Panagiotis Kanavos, Oct 08 '20 at 05:45

score 0 · Answer 1 · edited Jun 12 '21 at 18:38

You may follow this solution. I suggest you have two tables. One is for the master data, and the other is for localized data. For example:

Have main table e.g. Product, to contains master data like ProductCode, Name, Description, and also have a field named like ObjectGuid, to identify Product object uniqueness.
Have Localize Table, to contains translated data of Name, Description, and also have a field named like "Language" to identify language of Name, Descript. This table need to have OwnerGuid where linked to ObjectGuid.
Link Product to Localize with one-two-many relationship, using Product.ObjectGuid==Localize.OwnerGuid && UICulture.language==Localize.Language, where UICulture.language is provided by your user.

How to handle localized content in ASP.NET Core?

1 Answers1