Re: Fail to encode attachement filenames properly.

[Jinhyok Heo <novembre+dated+1020732359.ff68e2@ournature.org>]

>>>>> "JH" == Jesper Harder <harder@ifa.au.dk> writes:

    JH> novembre+dated+1020567757.8c22a8@ournature.org (Jinhyok Heo) writes:
    >  If I send a non-latin filename attachment, Gnus seems to fail to
    >  encode it properly.
    > 
    >  For example, a correct attachement mime part would start like the
    >  following.
    >  ,--------------------------------------------
    > Content-Type: application/octet-stream;
    >         name="=?euc-kr?B?tOuxuLGztbW80ijAzrHHwKew+LmuKS5od3A=?="
    > Content-Transfer-Encoding: base64
    > Content-Disposition: attachment;
    >         filename="=?euc-kr?B?tOuxuLGztbW80ijAzrHHwKew+LmuKS5od3A=?="
    >  `--------------------------------------------

    JH> This is not standards compliant.  The filename parameter should be
    JH> encoded using RFC 2231, not an RFC 2047 encoding as in your example.

Well, I didn't know that which one is standard comliant. I appreciate
your information.

The above one was excerpted from a M$-outlook mail.

    >  But my Gnus which I got it from cvs recently makes mime parts like
    >  ,--------------------------------------------
    > Content-Type: application/octet-stream
    > Content-Disposition: attachment;
    >   filename*=euc-kr''kin_%bc%b3%b9%ae%c1%f6.hwp
    > Content-Transfer-Encoding: base64
    >  `--------------------------------------------

    JH> This looks correct to me.

But people who use M$-outlook or many webmails have trouble with
attachments I send to them.

I just have to wait and see for M$-outlook to be standard compliant in
the future?

-- 
| Jinhyok Heo (novembre @ ournature.org || http://ournature.org/~novembre/)
|--------------------------------------------------------------------------
| "We are still reaching for the sky. In the developed countries people
|  are coming back down, saying, `It's empty up there.'" --- a Ladakhi monk