Heiko Voigt <[EMAIL PROTECTED]> wrote:
> > Are you sure it's not your filesystem that forbids those characters?
> > MacOS X can use ufs, right? Does it allow those characters there?
> >
> > Which characters, exactly, anyways?
>
> Its the characters 'äöü' which are in the latin1 table at 228,246,252.
> The filesystem is capable of these characters but it uses UTF-8 to
> encode them. I use HFS+ and have no ufs formatted drives on hand, so I
> can't test it at the moment.
HFS+ is not POSIX compliant. POSIX requires a case sensitive filesystem.
There may be more problems with HFS+
UTF-8 could only be the universal solution if there would be no other codings
out in the world.....
Creating a filesystem with fixed character encoding creates problems in a
multi user system (like UNIX) where each process may use it's own different
coding. This is why filesystems usually allow any non-null character in
path names and why UTF-8 has been defined in a way that makes sure that
no character > 127 uses a '/' inside any octet of it's coding.
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
_______________________________________________
Bug-tar mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-tar
