Mule bugs: misidentification (Latin-1 vs. Chinese), revert issues
kehoea at parhasard.net
Wed Jan 16 14:46:58 EST 2008
Ar an séú lá déag de mí Eanair, scríobh Glynn Clements:
> Stephen J. Turnbull wrote:
> > > And on OS X file-name-coding-system (and relatedly, the 'file-name
> > > coding system alias) is unconditionally UTF-8, independent of the
> > > locale coding system.
> > This is a good heuristic, since the most popular file system on OS X
> > is HFS+, which does try to enforce UTF-8 file names.
> Although, OSX encodes accented characters using combining accents
> rather than using pre-composed characters. IIRC, OS functions will
> decompose any pre-composed characters automatically, but you need to
> bear in mind that a byte string obtained from e.g. readdir() won't
> necessarily match the byte string you passed when creating the file.
Yeah; that’s something we don’t bear in mind at the moment, unfortunately.
> Needless to say, Unix/Linux just treats composed/decomposed versions
> of the same text as entirely different filenames.
Yes! Of course /tmp/ä and /tmp/ä are distinct files! Perhaps a smidgin more
surprising is that NTFS does too, to my knowledge.
¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
More information about the XEmacs-Beta