Re: [w3c/IndexedDB] Add locale-aware sorting (#38)

@sicking Dealing with key equality can be done such that two distinctly encoded keys (that compare as equivalent according to UCA+tailoring) are not considered equal. There is a long section in [UTS10](http://www.unicode.org/reports/tr10/#Deterministic_Sorting) about the topic. Having this be stable could be a requirement.

A different consideration is whether two implementations need to produce identical sort orders given the same inputs (data values). If, say, FF has CLDR v28 and Chrome has CLDR v29, are they required to sort lists in the locale 'fr-FR' identically or not, if the underlying CLDR data has changed? Annual versions of Unicode and semi-annual ones of CLDR complicate this. But there is real value in providing locale-based sorting. That's why every relational database I know supports it. The interop guarantee is, I guess, the thorny issue here.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/38#issuecomment-289154003