Datetime formatting issue

[ohba-ikuo]

Oqtane Info

Version - 5.1.1
Render Mode - Static
Interactivity - Server
Database - SQL Server

Describe the bug

When transitioning to visitor management in the Japanese location, an application error occurs.

[Event Log]

Expected Behavior

It is believed that an error will always occur when transitioning to Visitor Management in locations that use multibyte characters.

Steps To Reproduce

Anything else?

[ohba-ikuo]

@dotnet-policy-service agree From: dotnet-policy-service[bot] ***@***.***> Sent: Sunday, April 21, 2024 9:12 PM To: oqtane/oqtane.framework ***@***.***> Cc: 大場 育雄 ***@***.***>; Mention ***@***.***> Subject: Re: [oqtane/oqtane.framework] Datetime formatting issue (PR #4164) @ohba-ikuo<https://github.com/ohba-ikuo> the command you issued was incorrect. Please try again. Examples are: @dotnet-policy-service agree and @dotnet-policy-service agree company="your company" — Reply to this email directly, view it on GitHub<#4164 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A635CLLB7335FU5CGEYP2G3Y6OUINAVCNFSM6AAAAABGRKIDZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGAZDCNZVGI>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[leigh-pointer]

Hi @ohba-ikuo are you using Oqtane with the default language or have you created a Japanese language pack?

[sbwalker]

@ohba-ikuo thank you for reporting. I can see that multi-byte characters can cause some Internationalization challenges when using MMM format. The reason why the dd-MMM-yyyy format was chosen was so that there would be no ambiguity between months and days. For example, is 2023-03-01 equivalent to March 1 or January 3? I assume that the date needs to be encoded and decoded using the same Culture for this to work properly - which is not being explicitly specified in Oqtane currently as it is using DateTime.Parse(fromdate).

[ohba-ikuo]

@sbwalker
Thank you for your response. I now understand why you are using the "dd-MMM-yyyy" format for the date.

[ohba-ikuo]

@dotnet-policy-service agree

[sbwalker]

Thank you for making these changes... this is the recommended pattern for handling i18n (internationalization) for dates and it works well in Urls because there are no extended characters which need to be encoded.