"Anton B. Rang" <[EMAIL PROTECTED]> wrote:
> Yes -- that's why Apple includes an encoding byte in both HFS and HFS+. (In
> HFS+, filenames are normalized to 16-bit Unicode, but the encoding is still
> useful in choosing how to recompose the characters, and in providing hints
> for applications which prefer the names in some 8-bit encoding.)
If you like to do something like this, it would be better to use the UDF
aproach.
In UDF directories, the first byte of a filename may either be 8 ('\010') and
then the filename is ISO-8859-1 (the low 8 bits of UNOICODE) or 16 ('\020') and
then the file name is usinf UCS-2 (16 bit chars) from UNICODE.
This allows to keep the full path name length for the popular ISO-8859-1
coding and still needs less space than UTF-8 if you e.g. use japanese chars as
Japanese chars need 3 octects in UTF-8.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
