unicode filenames

Ganesan R rganesan at myrealbox.com
Mon Feb 3 13:15:45 CET 2003


>>>>> "Ganesan" == Ganesan R <rganesan at myrealbox.com> writes:

>>>>> "Alex" == Alex Martelli <aleax at aleax.it> writes:

>> Ah!  Wonderful, thanks -- and clearly this was one crucial
>> point I was missing: UTF-8 *IS* "specifically and carefully 
>> designed to avoid ever needing a byte of value 47 (0x2F) in 
>> order to represent ANY character except a slash" (among
>> other things;-), and therefore _IS_ usable as the encoding
>> of Unicode names on a non-Unicode-aware Unix system.

> Indeed. UTF-8 had it's origin in Plan 9 (if I remember correctly) as
> a "File System Safe" unicode tranformation formation. You can find a
> document titled FSS-UTF on the net.

Sorry to follow up on my own post, but I was incorrect. It appears that
UTF-FSS first appeared as an X/Open document authored by an IBM
employee. See 
http://www.mail-archive.com/linux-utf8@nl.linux.org/msg03609.html

Ganesan

-- 
Ganesan R





More information about the Python-list mailing list