Re: [Bug-tar] mac os x or general charset problem patch

[Heiko Voigt]

Hi,

On 10.12.2005, at 10:35am, Paul Eggert wrote:
> Was the "\377" four different characters "\", "3", "3", "7", or does
> this represent a single byte in the actual tar output?

The \337 represents a single byte. It is libc who is denying to write 
this kind of
character.

> That "(null)" indicates that something went seriously wrong on your
> host, in that errno was set to a value such that strerror (errno)
> returned a null pointer.  Can you use a debugger to see what might
> have caused that?  Perhaps, if we can fix the underlying problem, then
> we won't need the quick and dirty workaround that you mentioned.

I the original message was from the preinstalled tar of mac os x. If I 
use the compiled it says:

/Users/scho/download/temp/tar-1.15.1/src/tar: 
\366\374\344\337.\344\374\366: Cannot open: Invalid argument

this was a testfile with 7 national characters.

So strerror just doesn't work on the preinstalled version.


Joerg wrote:
> The error message looks like it has been caused by a gtar bug.

I compiled tar from here http://www.gnu.org/software/tar/ joerg what do 
you mean with gtar?


Sergey wrote:
> It seems to be an operating system issue, rather than tar's one. I 
> think
> setting right locale will allow you to use national characters in file
> names.

In my opinion tar should be able to extract files even if the 
characterset is different. Its just a hassle for the user if he has to 
guess in which the archive was packed. tar should probably also output 
warning that it could not extract a filename correctly.

cheers Heiko