Hi Jeffrey! On 6 May 2008, at 20:22, Jeffrey Altman wrote:
Garrett Wollman wrote:<<On Tue, 06 May 2008 10:04:17 -0400, Jeffrey Altman <[EMAIL PROTECTED] > said:1. MacOS X and Linux clients begin to apply NFC to all UTF-8 strings obtained from the operating system whether for directory lookup,object creation, or symlink target creation.How do they know it's a UTF-8 string? Traditional Unix semantics provide that a file name is a byte sequence, not a character sequence.There are algorithms you can use to validate utf-8 sequences.
Well, certainly. But I find it very irritating that a filesystem should somehow interpret and _change_ a filename based on the assumption of UTF-8 encoding, even if the filename's byte sequence happens to conform to the UTF-8 rules. Why bother? It's much easier and much more portable to regard filenames as opaque byte sequences.
I appreciate that don't have contributed much, so you are free to ignore my ranting, but if there's a technical problem with the above, I'd really like to hear the arguments, even in sketchy form.
Ciao,
Roland
--
Any society that would give up a little liberty to gain a little
security will deserve neither and lose both. - Benjamin Franklin
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GS/CS/M/MU d-(++) s:+ a-> C+++ UL++++ P+++ L+++ E(+) W+ !N K- w--- M+ !
V Y+
PGP++ t+(++) 5 R+ tv-- b+ DI++ e++++ h---- y+++ ------END GEEK CODE BLOCK------
PGP.sig
Description: This is a digitally signed message part
