[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: uuencode: multi-bytes char in remote file name contains bytes >0x80
From: |
Eric |
Subject: |
Re: uuencode: multi-bytes char in remote file name contains bytes >0x80 |
Date: |
Thu, 7 Jul 2011 01:17:54 +0800 |
Hi all:
If there are characters in decode_pathname that are not in the portable
filename character set the results are unspecified.
I think we could do some work to solve the non-ASCII file name problem
according to the above feature. the implementation is not a problem, the
point is whether it is necessary or not to do so ( add an option for uuencode),
if not, then we would use other tools to solve the problem; otherwise we
could discuss on how to implement.
so is it necessary to add an option to uuencode?
--
best wishes, Eric
- Re: uuencode: multi-bytes char in remote file name contains bytes >0x80, (continued)
- Re: uuencode: multi-bytes char in remote file name contains bytes >0x80, Bruce Korb, 2011/07/05
- Re: uuencode: multi-bytes char in remote file name contains bytes >0x80, Eric Blake, 2011/07/05
- Re: uuencode: multi-bytes char in remote file name contains bytes >0x80, Bruce Korb, 2011/07/05
- Re: uuencode: multi-bytes char in remote file name contains bytes >0x80, Eric Blake, 2011/07/05
- Re: uuencode: multi-bytes char in remote file name contains bytes >0x80, Bruce Korb, 2011/07/05
- Re: uuencode: multi-bytes char in remote file name contains bytes >0x80, ��叁, 2011/07/06
- Re: uuencode: multi-bytes char in remote file name contains bytes >0x80, Eli Zaretskii, 2011/07/06
- Re: locale encodings, Bruno Haible, 2011/07/05
Re: uuencode: multi-bytes char in remote file name contains bytes >0x80,
Eric <=