Create new doc article on handling server side and client side culture on ASP.NET

[eriawan]

Describe the new topic

• This topic is highly needed because currently in the docs pages there's no article that describe server side and client side culture handling in ASP.NET Core 2.2, as described in issue Show support jQuery validation for non-English locales that use a comma (",") for a decimal point #4076
• This culture handling topic should be located under "Globalization and localization".

Abstract

• Describe server-side culture feature in ASP.NET Core 2.2 and handling them (with sample code)
• Describe client-side culture feature in ASP.NET Core 2.2 and handling them (with sample code)
• incorporate sample validation as described in Show support jQuery validation for non-English locales that use a comma (",") for a decimal point #4076

Items to track

• Handle client-side (user agent's) culture from server side culture and sample code
• Handle client-side (user agent's) culture from client-side culture handling and sample code, using AcceptLanguageHeaderRequestCultureProvider in combination with jQuery
• Use validation sample as another sample case with code

NOTES: other contents will be added later

cc @Rick-Anderson

I welcome feedback 🙂

[hishamco]

Describe server-side culture feature in ASP.NET Core 2.1 and handling them (with sample code)

If you mean providing culture using IRequestCultureProvider the current docs already describes this, also AcceptLanguageHeaderRequestCultureProvider described there, i'm not sure what you will add, but I write my comments later

thanks

[eriawan]

@hishamco

Thanks!
Yes, current doc already describes that. I may as well add the needed case on client side while also add more detail on server side. My WIP may or may not be in the form of new page.

[hishamco]

I may as well add the needed case on client side while also add more detail on server side

Could you please elaborate?

[eriawan]

I mean, for client side I will try to integrate with the previous problem when handling with jquery validation, and also try to have one sample that has handling for both server-side and client-side culture.

[Rick-Anderson]

@ryanbrandenburg please review outline.

[ryanbrandenburg]

By outline do you mean the items under the abstract heading? What's there is fine, but it doesn't give me much of an idea of what the doc will look like or say.

[Rick-Anderson]

@eriawan go ahead.

[eriawan]

@Rick-Anderson
thanks! I will start tomorrow.

[ryanbrandenburg]

Seems like this is on @eriawan's plate now. If there was still an action item for me here re-assign me with a description of what needs done.

[Rick-Anderson]

Thanks @ryanbrandenburg just wanted to verify you were OK with the plan.

[eriawan]

Yes, the work is still ongoing.
I have updated the abstract above to indicate that the page will describe and emphasize handling client-side culture from server-side and client side.

[hishamco]

@eriawan can create a WIP PR so we can see what's going on, also it's good to get the feedback at the early stages

[eriawan]

@hishamco
I agree, thanks for the help 🙂
yes, I will put the PR after I finish testing my code against some web browsers first.

[hishamco]

@eriawan any update on this?

[eriawan]

@hishamco

hang on, my testing to many web browsers about this feature is done, also because I've also tested the upgrade to .net core 2.1.500 SDK and test on it too. I'm alsoe adding some highlights comparing to core 2.0.

I'll push it soon within next week, please be patient 🙂

[FFMartin]

@eriawan
Any update on the subject ?

[eriawan]

@FFMartin
testing is done! the page will be ready, with additional info for .NET Core 2.2 to keep up with.
please be patient 🙂

[dotVip]

Any update on the subject ?

[eriawan]

@dotVip

The article will be ready around end February, with samples on .NET Core 2.1 and 2.2 and interop with server side. Please be patient 🙂

[Rick-Anderson]

@eriawan I wouldn't worry about 2.1

[guillos]

Any Update? I´m stuck on this and don´t know what to do...

[eriawan]

@Rick-Anderson
yes, I think 3.1 is better and it should be not much different on 5.0.

thanks for your patience! I'm still testing it, especially on the latest Chrome, Firefox and MS Edge beta that uses Chromium.

[Rick-Anderson]

@dannevesdantas always looking for help.

[hishamco]

Me too 😄, but I'm not sure why this takes so long, without any draft?!!

[dannevesdantas]

Can we help in some way @eriawan? Do you need some help?

[hishamco]

@eriawan any updates on this one, could you please push a draft PR, so we can help you

[eriawan]

@hishamco

please be patient, I'm still migrating the code to .NET Core 3.1

[hishamco]

My intend to help you nothing else, coz this issue takes long time

[ericvb]

What is the current status?

[hishamco]

Any progress on this one?

[Rick-Anderson]

@eriawan anything we can do to help? .NET 6 is all we need.

[eriawan]

@Rick-Anderson

My bad, I apologize.
Let me revisit and try to come up wip in a week.

[hishamco]

I suggest to send WIP PR, we can all help you on this

[Rick-Anderson]

@eriawan anything we can do to help? .NET 7 is all we need.

[hishamco]

This issues has no progress since 4 years unless there's a local branch doesn't push, again anything we can help you?

[eriawan]

@Rick-Anderson
I'm deeply sorry I had taken this too long and I also I had to switch jobs during pandemic.
I have had work this on my work for .NET 6 and as suggested, I'm goiing to continue to put for .NET 7.
For .NET 7 I should use VS 2022 17.4 Preview with .NET 7 SDK Preview, right?

[Rick-Anderson]

For .NET 7 I should use VS 2022 17.4 Preview with .NET 7 SDK Preview, right?

I'm on Version 17.4.0 Preview 2.0 today. Use the most current version.

[Rick-Anderson]

@eriawan Just use .NET 7.

[hishamco]

Could you please post a WIP PR, this took more than two years

[Rick-Anderson]

@eriawan any ETA. You can use .NET 8

[hishamco]

@Rick-Anderson this has taken too long, is there anything here to help you with?

[Rick-Anderson]

I'll close the issue. IF @eriawan makes a PR, we can re-open.

[Ragowit]

I really hope to see an update, since culture/localization is very important to all of us with more then just English as language. But yeah, it's been 6 years now...

[hishamco]

@Ragowit is there anything in particular you need to update?

[Ragowit]

@hishamco I have switched job over the last six years so I don't work with ASP.NET anymore. But I'm still keeping an eye on this out of interest.

[hishamco]

All the best