Markus Scherer

> I've got a use case where I can't do direct comparisons of the strings, and so sort keys are the only available solution. Could you please say more about...

> Re-opening to seek additional feedback from @markusicu and @hsivonen I don’t have much to add to the discussion. Sort keys have a cost (extra code, processing time, storage) but...

> I will point out that it is error-prone to use collation ordering as a key in a database. You need to be ready to rebuild your indexes whenever upgrading...

Just to be clear, from my perspective: - We try to steer people away from sort keys *if they don't really need them*. - For some use cases, you do...

Hi @annevk, regarding > Steps don't always consider that domain labels can be empty, e.g., when CheckBidi is true the first subrule of "The Bidi Rule" inspects the first character...

Looking at “the ContextJ rules”, https://www.rfc-editor.org/rfc/rfc5892.html#appendix-A processes a label with a pseudo-code loop of `For All Characters`. On an empty label, this is an empty loop. For CheckBidi, I see...

Alternative change: We could make this small insertion at the beginning of 4.1 Validity Criteria: “Each of the following criteria must be satisfied for a non-empty label”

I am not vested in these three characters, or possible future ones with this behavior. Clearly the UTS46 rule is based on their Decomposition_Mapping, but UTS46 does use NFC compositions,...

tentative feedback lgtm

> Another way to attack this, that would be much faster, is not try resource fallback for every one of the variants in a locale. > > Instead, do a...