- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Sat, 29 Sep 2018 17:39:16 +0000
- To: public-i18n-archive@w3.org
@svgeesus Thanks for the reply. Adding casefolding adds a level of complexity that you might not want, since it generally brings with it the need to do text normalization or the need to case fold only ASCII characters. My personal suggestion would be to do strict Unicode code point ordering, since the goal of the sort doesn't appear to be to produce any specific order. @stpeter is right that the id value can be any DOMString, at least technically. But the original text commented appears to be providing a deterministic way of choosing arbitrarily when there is more than one audio item. Either ASCII or Unicode case insensitive comparison requires more plumbing than is needed to do that (there is a tiny bias in favor of implementations that use uppercase in UUIDs, but not enough to make it worth the effort??) -- GitHub Notification of comment by aphillips Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/598#issuecomment-425662690 using your GitHub account
Received on Saturday, 29 September 2018 17:39:22 UTC