[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: Bruce Korb
Subject: Re: uuencode: multi-bytes char in remote file name contains bytes >0x80
Date: Wed, 06 Jul 2011 13:21:29 -0700
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110616 SUSE/3.1.11 Thunderbird/3.1.11

On 07/06/11 12:55, Bruno Haible wrote:
Bruce Korb wrote:
I think the arguments are sufficient to make the changes.
The change will include uudecode changes so it can detect
and handle the encoded file names, and uudecode will get
an "encode-filename" ("-e") option.

Where and how will the charset conversion of the filenames be handled?

Yes, it will be.

There are two ways to deal with it:
   a) Do the charset conversion on the receiver's side, and on the sender's
      side only embed the charset. The most well-known encoding of this
      kind is probably the way subject lines are encoded in MIME:
      "jörg" would become
   b) Do the charset conversion both on the sender's side and on the
      receiver's side, and always send filenames converted to UTF-8.

I pick the way that is most robust and prone to the fewest problems.
You tell me, please. :)  I'll do what you suggest and run the result
past both you and our new friend, =?GB2312?B?j4jI/g==?=

Cheers - Bruce

reply via email to

[Prev in Thread] Current Thread [Next in Thread]