DefaultCurrentThreadCulture Remark is Ambiguous

[nagilson]

On this page, https://learn.microsoft.com/en-us/dotnet/api/system.globalization.cultureinfo.defaultthreadcurrentculture?redirectedfrom=MSDN&view=net-7.0#remarks, there is a remark which states the following:

If you have not explicitly set the culture of any existing threads executing in an application domain, setting the [DefaultThreadCurrentCulture](https://learn.microsoft.com/en-us/dotnet/api/system.globalization.cultureinfo.defaultthreadcurrentculture?view=net-7.0) property also changes the culture of these threads. However, if these threads execute in another application domain, their culture is defined by the [DefaultThreadCurrentCulture](https://learn.microsoft.com/en-us/dotnet/api/system.globalization.cultureinfo.defaultthreadcurrentculture?view=net-7.0) property in that application domain or, if no default value is defined, by the default system culture.

I think the typo(s) make this a bit unclear, is it:

If

1. These threads execute in another application domain
2. Their culture is defined by the [DefaultThreadCurrentCulture] property
3. No default value is defined by the default system culture

Then
DefaultThreadCurrentCulture won't take effect, so you need to set CurrentUICulture? I think it could be made a bit more clear how 2 and 3 are different, as well as how is it possible that the DefaultThreadCurrentCulture culture doesn't work if it is defined by DefaultThreadCurrentCulture?

Tagging subscribers to this area: @dotnet/area-system-globalization
See info in area-owners.md if you want to be subscribed.

Issue Details

---

On this page, https://learn.microsoft.com/en-us/dotnet/api/system.globalization.cultureinfo.defaultthreadcurrentculture?redirectedfrom=MSDN&view=net-7.0#remarks, there is a remark which states the following:

If you have not explicitly set the culture of any existing threads executing in an application domain, setting the [DefaultThreadCurrentCulture](https://learn.microsoft.com/en-us/dotnet/api/system.globalization.cultureinfo.defaultthreadcurrentculture?view=net-7.0) property also changes the culture of these threads. However, if these threads execute in another application domain, their culture is defined by the [DefaultThreadCurrentCulture](https://learn.microsoft.com/en-us/dotnet/api/system.globalization.cultureinfo.defaultthreadcurrentculture?view=net-7.0) property in that application domain or, if no default value is defined, by the default system culture.

I think the typo(s) make this a bit unclear, is it:

If

1. These threads execute in another application domain
2. Their culture is defined by the [DefaultThreadCurrentCulture] property
3. No default value is defined by the default system culture

Then
DefaultThreadCurrentCulture won't take effect, so you need to set CurrentUICulture?

Author:	nagilson
Assignees:	-
Labels:	untriaged, Pri3, area-System.Globalization
Milestone:	-

[tarekgh]

@nagilson thanks for your report. Feel free to submit a PR if you like.

[nagilson]

I would be down to, but I can't understand what it does from the current docs, so anything I write may be misinformation.
@tarekgh do you have any contacts who could better describe what this is trying to get at? Thanks!

[tarekgh]

do you have any contacts who could better describe what this is trying to get at?

That would be me :-)

[nagilson]

I think this remark is a bit old and meant for .NET Framework apps, and so for .NET Core apps it's not much of a concern.