NativeName on CurrentCulture is shorten on Blazor WebAssembly .NET 5.0

[christianzingg]

The following Code produces different output comparing Blazor WebAssembly 3.2.0 and 5.0.0:

Thread.CurrentThread.CurrentCulture = new CultureInfo("en-US");
var native = Thread.CurrentThread.CurrentCulture.NativeName;
Console.WriteLine(native);

Blazor WebAssembly 5.0.0 --> "en (US)"
Blazor WebAssembly 3.2.0 --> "English (United States)"

PS: On normal ASP-Web application running with .NET 5.0 the output is "English (United States)"

[ghost]

Tagging subscribers to this area: @tarekgh, @safern, @krwq
See info in area-owners.md if you want to be subscribed.

Issue Details

Description:	The following Code produces different output comparing Blazor WebAssembly 3.2.0 and 5.0.0: Thread.CurrentThread.CurrentCulture = new CultureInfo("en-US"); var native = Thread.CurrentThread.CurrentCulture.NativeName; Console.WriteLine(native); Blazor WebAssembly 5.0.0 --> "en (US)" Blazor WebAssembly 3.2.0 --> "English (United States)" PS: On normal ASP-Web application running with .NET 5.0 the output is "English (United States)"
Author:	christianzingg
Assignees:	-
Labels:	area-System.Globalization, untriaged
Milestone:	-

[safern]

cc: @lewing @EgorBo

[csharpfritz]

This is a regression in .NET 5 compared to all of the other .NET frameworks. Please reconsider a patch to address this for our developers and users that don't speak English

Also: EnglishName property is misconfigured similarly

[tarekgh]

CC @tqiu8

[lewing]

This is intensional to save space, we might possibly be able to get some of this data from the browser Intl api. Moving to .NET 7

[csharpfritz]

I'm disappointed by the decision... but understand and will build a work-around index that contains these values in their native language Jeff

…

On Sat, Jul 31, 2021 at 3:51 PM Larry Ewing ***@***.***> wrote: This is intensional to save space, we might possibly be able to get some of this data from the browser Intl api. Moving to .NET 7 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#44739 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAATF4MBIRS7R7PF6RE5DRLT2RH4BANCNFSM4TXON6WA> .

[lewing]

@csharpfritz I'm disappointed too but we've run out of time to solve this more generally for .NET6.

[csharpfritz]

Completely understood and I appreciate your position as we enter August Jeff

…

On Sat, Jul 31, 2021 at 4:37 PM Larry Ewing ***@***.***> wrote: @csharpfritz <https://github.com/csharpfritz> I'm disappointed too but we've run out of time to solve this more generally for .NET6. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#44739 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAATF4JMRLVIUGKVW4B5SJ3T2RNILANCNFSM4TXON6WA> .

[Jinjinov]

So, the .NET 7 ship has sailed on this issue.

Can we expect this anytime soon? :)

I thought trimming was used to save space by removing unused code?

[csharpfritz]

Can we just move this feature to an external library that is optionally included in WebAssembly deployments?

At this point, I've written my own Dictionary object to host this content

[thomasgalliker]

I'm struggling with this issue on .NET MAUI (net8.0). Where can I find the native names of languages?

[ilonatommy]

It was not backported to 8.0 and it's available in HybridGlobalization mode that has its side-effects - doc.
@lewing, should we backport it?