3 ms·
NFD hadn't been standardized at the time. IIUC the reason they did this is that they wanted directories to be canonically ordered on disk, and they thought dec
by cryptonector 9y ago
NFD hadn't been standardized at the time.
IIUC the reason they did this is that they wanted directories to be canonically ordered on disk, and they thought decomposition would naturally yield better results than pre-composition. I'm not sure that's right, and frankly I don't care either, because the most important thing to note is that input methods (especially for European languages) by and large produce NFC, and most application software does no normalization at all, so disagreements as to form cause problems[0][1].
[0] https://cryptonector.com/2010/04/on-unicode-normalization-or-why-normalization-insensitivity-should-be-rule/ https://cryptonector.com/2010/04/on-unicode-normalization-or...
[1] https://cryptonector.com/2006/12/filesystem-i18n/ https://cryptonector.com/2006/12/filesystem-i18n/
- cryptonector 9y agoI should add that because different locales have different collations, it's not that important that directories be order by name. It's good enough that directories be somewhat ordered, and even that they not be at all. GUIs will almost always let you sort by name and/or date, and the same goes for ls(1), so, really, it doesn't matter at all. IMO it was a terrible mistake to normalize to NFD on create. Normalizing to NFC on create would still have been a mistake, but a lesser one.