Ienup Sung <[EMAIL PROTECTED]> wrote:
> > This would at least create incompatibilities with long filenames.
> > ISO-8859-1 is the low 8 bits of UNICODE and if I use a ISO-8859-1
> > coded filename I am currently able to have up to 255 ISO-8859-1
> > characters in a filename.
> >
> > After e.g. UFS is converted to UTF-8, the max file name length depends
> > on the content of a filename and may be reduced to only 127 ISO-8859-1
> > characters. As a result, you may be unable to restore a backup.
> >
> > Jörg
>
> That's true and so migration to UTF-8 FS and switch on or off of
> the feature is not mandatory. The migration is also aided by tools such as
> fsexam(1) that people can do dry run and customization after the dry run.
As ISO-8859-1 is the low 8 bit of UNICODE, it would be possible to
store UNICODE or ISO-8859-1 in a directory entry and to distinct
UTF-8 from ISO-8859-1. In this case, you need to allow longer file names than
255 bytes with lookuppn() but this is needed anyway for Joliet where you
would need up to 330 bytes + null character in order to store a
110 character file name that uses katakana only.
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
_______________________________________________
opensolaris-discuss mailing list
[email protected]
