We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
According to Unicode CLDR (here), the bo will have dateFormat as
bo
<availableFormats> <dateFormatItem id="GyMMM">G y LLLL</dateFormatItem> <dateFormatItem id="MMMd">MMMཚེས་d</dateFormatItem> <dateFormatItem id="MMMEd">MMMཚེས་d, E</dateFormatItem> <dateFormatItem id="MMMMd">MMMMའི་ཚེས་d</dateFormatItem> <dateFormatItem id="yMMM">y LLL</dateFormatItem> <dateFormatItem id="yMMMd">y ལོའི་MMMཚེས་d</dateFormatItem> <dateFormatItem id="yMMMMd">སྤྱི་ལོ་y MMMMའི་ཚེས་d</dateFormatItem> </availableFormats>
which is bo-CN actually from the YMD dateFormat order. The current longDateFormat of bo,
bo-CN
longDateFormat
longDateFormat : { LT : 'A h:mm', LTS : 'A h:mm:ss', L : 'DD/MM/YYYY', LL : 'D MMMM YYYY', LLL : 'D MMMM YYYY, A h:mm', LLLL : 'dddd, D MMMM YYYY, A h:mm' }
corresponds to bo-IN after I review the DMY date format on CLDR hi.
bo-IN
I suggest we rename bo locale to bo-IN and align bo date accordingly.
This will break locale name compatibility and we should document that the user of bo locale should choose between bo and bo-IN.
cc @vajradog
The text was updated successfully, but these errors were encountered:
@JLHwung I'd be happy to merge something that is in line with CLDR.
Sorry, something went wrong.
closing as part of #4949
No branches or pull requests
According to Unicode CLDR (here), the
bo
will have dateFormat aswhich is
bo-CN
actually from the YMD dateFormat order. The currentlongDateFormat
ofbo
,corresponds to
bo-IN
after I review the DMY date format on CLDR hi.I suggest we rename
bo
locale tobo-IN
and alignbo
date accordingly.This will break locale name compatibility and we should document that the user of
bo
locale should choose betweenbo
andbo-IN
.cc @vajradog
The text was updated successfully, but these errors were encountered: