2026-09-07 22:50 UTC
@futzle@old.mermaid.town I discovered collation rules existed when I fielded a bug report of results being returned in a different order on different hosts.
Turned out we used both US and AU collations, and they had different opinions about how to sort strings in Thai script, meaning the order of results using that script was inconsistent.
That was also the job where I discovered that U+2028 and U+2029 were valid unescaped characters in JSON, but not in javascript object literals, meaning you couldn't use `eval` in the browser to parse JSON (this has since been fixed in the relevant spec).
Replies (1)
-
@sabik@rants.au 2026-09-07 23:44
@knack@aus.social @futzle@old.mermaid.town My first fun with collation orders came from the split(1) command, which uses filenames like PREFIXaa, PREFIXab, ... for the pieces, and then in Czech, ch is a single letter which comes after h, so that one piece got misplaced when I did `cat PREFIX*` in Czech locale