Wrong standard unicode for Minutes #2834

[RobinHerbots]

See #2834

https://tc39.es/ecma262/multipage/numbers-and-dates.html#sec-date-time-string-format
https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings?view=netframework-4.7
https://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table

Standards are a good thing, however who decided to use M for months instead of m? Day and year are lowercase.... where is the logic?

[Techn1c4l]

I would say go for the standard. Standards are not always logical, but we're stuck with them.

Imagine the mask format is generated by some external system. To use your library (which is the best input masking library for JavaScript and other languages probably too), a developer would have to write a workaround converter.

For example, I have to do toLowerCase() for the date mask format string which I generate after recognizing system date format of the user, since it has MM for month. In this example, my work is pretty simple, but I would rather follow the standard.

[kl3sk]

I aggre with both @RobinHerbots and @Techn1c4l , it as some unlogical flaws but standard exists for a reason.

I have to convert the string too, because I have an other lib under that follows the standard.

Anyway, thank for you work @RobinHerbots

[RobinHerbots]

Hmm, even standards are difficult, .... pasted some extra links.

[kl3sk]

The unicode seems the most used.

As I see in your other links, they seems to follow the same pattern for Minutes and Month.

Correct me if I'm wrong.