Re: uuencode: multi-bytes char in remote file name contains bytes >0x80

[Bruce Korb]

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
>          =?iso-8859-1?Q?j=F6rg?=
>       or
>          =?utf-8?Q?j=C3=B6rg?=
>       or
>          hex-encode:3F69736F2D383835392D313F513F6A3D463672673F
>    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.
>       Example:
>          j=C3=B6rg
>       or
>          hex-encode:6AC3B67267

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