Embed Notice

@dalias oh, I don't doubt it. pretty much the only constant of dealing with Unicode is that there's always some way in which it can be more cursed.

And even once you go beyond the spec into dealing with the real world and all of the ways people do things that don't actually match the spec, or match the spec from 20 years ago and haven't been updated since, or the like.

I at one point had the fun of trying to implement some kind of sane cross-platform network filesystem filename normalization, in a way that did anything sensible given all the different ways in which different platforms handle filenames, including macOS which normalizes using some ancient frozen version of NFKC.

And then we had some applications that we needed to support on top of this which only supported legacy codepages so you needed to test them out with your system set to the appropriate locale in order to run them using various different legacy codepages.

Had a lot of fun getting my QA team to try and navigate the applications for testing when the interface was all in Hangul.