Globalization docs cleanup

[ilonatommy]

[EDIT by guardrex to add the metadata]

Issue description

Our globalization-localization docs are missing a few bits that are in https://github.com/dotnet/runtime/blob/89bba37a92053f52e38d5a5c81a1f3510319dabf/docs/design/features/globalization-icu-wasm.md.

Suggested location to add these bits:
https://learn.microsoft.com/en-us/aspnet/core/blazor/globalization-localization
OR
https://learn.microsoft.com/en-us/dotnet/core/extensions/globalization-icu
(not sure what is neater)

We want to move the information about:

• shards (icudt.*.dat), the data each shard contains (1st paragraph)
• The 2nd paragraph can be copied but using blazor propery BlazorIcuDataFileName instead of WasmIcuDataFileName. The custom ICU can be mentioned with a link to the github doc - https://github.com/dotnet/runtime/blob/89bba37a92053f52e38d5a5c81a1f3510319dabf/docs/design/features/globalization-icu-wasm.md#custom-icu. It is considered a workaround way for corner cases and manual ICU build is not guaranteed to work with all filters configuration, so I would prefer to treat it as instruction for "advanced" users.
• The paragraph describing what BlazorWebAssemblyLoadAllGlobalizationData does.

Software versions

It should be applied to version .NET Core 8 and later.

Other remarks:

• https://learn.microsoft.com/en-us/dotnet/core/extensions/globalization-icu#icu-on-webassembly is very hard to understand. I am suspecting it contains limitations that were valid for an experimental HybridGlobalization feature that was disabled in [browser] Remove WASM HybridGlobalization from runtime code runtime#110567. It should be removed for net10. If you choose to place the blazor globalization switches update there, it can replace fully "icu-on-webassembly" paragraph.
• In case we would be adding the updates in "globalization-icu", let's add a cross link to it to "blazor/globalization-localization" and the other way around.

---

Document Details

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

• ID: 15e7c51d-1839-1849-813a-23c4d21c64ae
• Version Independent ID: d6f07538-228e-9f96-680f-6c324caf11d6
• Platform ID: bd2a8fe1-da71-2bfb-045d-1b5f49d944a4
• Content: ASP.NET Core Blazor globalization and localization
• Content Source: aspnetcore/blazor/globalization-localization.md
• Service: aspnet-core
• Sub-service: blazor
• GitHub Login: @guardrex
• Microsoft Alias: wpickett

[guardrex]

@danroth27 to triage on the where question because if it goes into the .NET Core docs an issue over there will track the updates with two notes ...

• BlazorWebAssemblyLoadAllGlobalizationData is used by the Blazor doc in three scenarios that are covered. However, it should still have a better explanation on what it does in this article.

• On "let's add a cross link to it to "blazor/globalization-localization" and the other way around" ... This is already present in the Blazor article in the following section ...

  https://learn.microsoft.com/en-us/aspnet/core/blazor/globalization-localization?view=aspnetcore-9.0#net-globalization-and-international-components-for-unicode-icu-support-blazor-webassembly

  ... but I can't say (yet) if the text in that section remains accurate. It hasn't been checked/updated for many years, so it probably doesn't capture any changes that were made to the globalization-icu-wasm.md markdown file over the years.

Also, note that if an issue is opened from the bottom of a Blazor article, the labeling, Blazor.Docs project, and tracking metadata are added automatically to the issue. I'll take care of them manually here.

[ilonatommy]

https://learn.microsoft.com/en-us/aspnet/core/blazor/globalization-localization?view=aspnetcore-9.0#net-globalization-and-international-components-for-unicode-icu-support-blazor-webassembly

So we DO have it in learning docs. Thank you, I could not find it.

... but I can't say (yet) if the text in that section remains accurate. It hasn't been checked/updated for many years, so it probably doesn't capture any changes that were made to the globalization-icu-wasm.md markdown file over the years.

The sentence "NET tooling to ease the process of creating the file is planned for .NET 10 in November, 2025" is not accurate, there is no tooling in net10 as there are not many users of corner cases it adresses. We did not get community interest in improving that process either.

I believe we have 2 options now:

• Apply what I initially suggested right in this link
• Or just make the docs better "searchable" - we could add a bit longer description in this link, that would be mentioning the property names that are discussed in the github doc.

Also, note that if an issue is opened from the bottom of a Blazor article, the labeling, Blazor.Docs project, and tracking metadata are added automatically to the issue. I'll take care of them manually here.

Thanks, I did not know it makes a difference.

[guardrex]

IIRC, that tooling remark for .NET 10 came from somewhere by someone 😄. I'll research it and get back to you shortly.

[guardrex]

Ok ... I see why it was stated. For your issue ...

dotnet/runtime#82908

... it had an original milestone of 8.0 ... then it was kicked to 9.0 ... then to 10.0 ... and then Pavel changed it to "Future" on Dec. 12 of last year.

I would've updated this section of the Blazor article for sure because it has my inline HTML comment ("UPDATE 10.0"), which are all tracked down and updated by GA. It's also tracked in my annual "UE" (User Experience) tracking issue for 2025 at #34434.

Anyway ...... that's simple enough to fix, and I'll take care of it, along with a better description of BlazorWebAssemblyLoadAllGlobalizationData.

We just need @danroth27 to triage which of your options he would like to pursue for the rest of the coverage. I should be able to reach this issue within a week ... I hope! ⛰️⛏️😅 I'll try.