Aspnetcore.docs: 3.0 update: Globalization and localization

[Rick-Anderson]

Ryan to do this.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d1833676-ff1b-c587-cc9c-81afffa8ef68
• Version Independent ID: ad989395-3f49-4d55-521e-cf6fe56281ee
• Content: Globalization and localization in ASP.NET Core
• Content Source: aspnetcore/fundamentals/localization.md
• Product: aspnet-core
• Technology: aspnetcore-fundamentals
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande

[hishamco]

@Rick-Anderson can I participate on this while I added almost the localization features if not all in 3.0.0 :)

[Rick-Anderson]

@hishamco Can you provide a PR with the 3.0 updates? You might want to duplicate the entire document like this:

::: moniker range=">= aspnetcore-3.0"
copy of existing doc which you update for 3.0
::: moniker-end

::: moniker range="< aspnetcore-3.0"

original document
::: moniker-end

[hishamco]

::: moniker range=">= aspnetcore-3.0"
copy of existing doc which you update for 3.0
::: moniker-end

Sure, I already know the monikers stuff :)

[hishamco]

FYI: I wrote a related blog post http://hishambinateya.com/what-is-new-in-localization-in-asp.net-core-3.0

[jjamid]

This guide is great for application localization.

Is there any built-in way to localize a razor component library as stand alone ? (i.e. all the resx files should be inside the library itself, etc...).

I read a few guides already and they all target only localizing an application.

[hishamco]

There's a built in support for that with the help of ResourcesLocationAttribute

[jjamid]

Thanks. I'll look into that.
Do you know of any guides/example that can help with this specific scenario ?

The desired result is having built-in resx files for the library for common languages, and still allowing to override specific values/add new languages by the consumer of the library also through localization.

[hishamco]

The current docs mentioning that also you can check aspnet/entropy repo

[hishamco]

@casee these are examples from the source

https://github.com/aspnet/Extensions/tree/master/src/Localization/Localization/test/Microsoft.Extensions.Localization.RootNamespace.Tests

https://github.com/aspnet/AspNetCore/tree/master/src/Middleware/Localization/testassets

They are absolutely will help you

[hishamco]

I think it's the time to start on this one

@Rick-Anderson shall I start with modifying the current code to target 3.0, after that we can write about the new stuff that have been added

[Rick-Anderson]

@Rick-Anderson shall I start with modifying the current code to target 3.0,

Sure. Just remember

::: moniker range=">= aspnetcore-3.0"
copy of existing doc which you update for 3.0
::: moniker-end

::: moniker range="< aspnetcore-3.0"

original document
::: moniker-end

[hishamco]

Don't worry about the monikers, I already worked with them before :)

the PR is coming 🚀 🚀 🚀

[hishamco]

@Rick-Anderson I will create another PR to talk about the Content-Language header, one more thing there's a minor change in LogLevel when the culture is unsupported shall we point to this?

[Rick-Anderson]

there's a minor change in LogLevel when the culture is unsupported shall we point to this?

Sure

[hishamco]

Ok, I will did that in my 2nd PR