Heiko Voigt <[EMAIL PROTECTED]> wrote:
> Thats basically what I am suggesting. If an attempt to write the
> correct characterset fail, tar should switch to the printable ASCII
> chars only and have some substitution mechanism for the unknown
> characters.
The official behavior is to skip files that cannot be extracted on the local
system.
If you like, you may run a second extract and use the -s/from/to/ option
to rename your secific file.
Doing this automatically is a bad idea as it will never be correct for
all cases. Even autodetection is nearly impossible as there is no error
code for filenames that are "invalid" on a local base.
Note that UNIX only forbids one single character: '\0', which is the
end marker. POSIX in theory could allow to restrict this but as nobody
did so far request to add a note to the error section of open(), it seems
that there is no interest to restrict the character set in the real world.
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
