3 ms·
> In Turkish, for instance, the dotted and dotless letter I are two different letters, unlike languages where dotless uppercase I corresponds to dotted lowercas
by yellowapple 8y ago
> In Turkish, for instance, the dotted and dotless letter I are two different letters, unlike languages where dotless uppercase I corresponds to dotted lowercase i.
In this case, I'd argue that Unicode should provide codepoints for Turkish-specific versions of these letters (or at the very least a separate codepoint for a capitalized version of a dotless 'i', such that it can always be assumed that the Latin uppercase I is meant to be dotted and can be displayed as such when using a Turkish locale). Alternately, the Turkish alphabet should have its own Unicode codepoints entirely, thus circumventing this issue (just like how Latin A != Cyrillic А != Greek Α).
> the Linux kernel source tree itself has include/uapi/linux/netfilter/xt_rateest.h and include/uapi/linux/netfilter/xt_RATEEST.h with different contents.
That's a rather horrific code smell, and I'm surprised Linus didn't chew someone out on the LKML over it. If they have different contents, then they should have meaningfully-different names (in this case, maybe xt_rateest_target.h v. xt_rateest_match.h?). It looks like there might be other files there with the same issue, and they should be fixed, too (as should any other files that reference those headers).
Like, just because it's possible to stick the barrel of a loaded 12-gauge in your mouth doesn't mean it's a good idea to do so.
- geofft 8y agoI don't necessarily disagree with either of these, but Unicode got encoded as it was and Linux got these files with these names and we can't go back and change it. (Even if the files get renamed, we have git history and stable release branches to think about.) The point of software is to deal with the world as it is, not as it should be. We've got pseudocode and research papers for the world as it should be.
- yellowapple 8y agoWe absolutely can change Unicode (that happens all the time, unless you think we've had emoji since the 90's), and we absolutely can rename those files (as they should be anyway, regardless of whether the filesystem is case-insensitive). If you need to dig through the git history or work with a branch that does not have that fix, then you can always mount a case-sensitive FS specifically for that purpose.