- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Sep 2018 16:21:42 +0000
- To: public-i18n-archive@w3.org
Thanks for your comment. We discussed it on todays telcon. We agree that "alphabetically" is imprecise and that we should order by Unicode codepoint. We are not yet sure on whether to do case folding, but suspect that this is indeed a good idea. > RFC 4122 section 3 requires that the characters to be generated in lower case, while being case insensitive on input, though some commonly-used implementations violate this rule. https://en.wikipedia.org/wiki/Universally_unique_identifier So these are 128bit numbers represented to users (and input) as hex strings and thus, constrained to US-ASCII. Given the RFC recommends converting to lowercase on input, and as in practice implementations don't all do that, ASCII case-insensitive (as used by for example CSS) seems like an appropriate method. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/598#issuecomment-425155421 using your GitHub account
Received on Thursday, 27 September 2018 16:21:44 UTC