From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Fail to encode attachment filenames properly.
Date: Thu, 02 May 2002 20:18:12 +0200 [thread overview]
Message-ID: <m33cxabehn.fsf@defun.localdomain> (raw)
In-Reply-To: <microsoft-free.3og01a3oqa.fsf@ournature.org> (novembre+dated+1020762014.ee9fa2@ournature.org's message of "Thu, 2 May 2002 14:11:12 +0000 (UTC)")
novembre+dated+1020762014.ee9fa2@ournature.org (Jinhyok Heo) writes:
>>>>>> "JH" == Jesper Harder <harder@ifa.au.dk> writes:
>
> JH> That could be a long wait :-) In the mean time (defalias
> JH> 'mail-header-encode-parameter 'rfc2045-encode-string) should
> JH> make Gnus use the "wrong" encoding, which Outlook can decode.
>
> Your suggestion doesn't solve the problem.
>
> For example, with the setting above. An attachment filename generated
> the following.
>
> |Content-Type: application/octet-stream
> |Content-Disposition: attachment; filename=020415~~~.hwp
> |Content-Transfer-Encoding: base64
>
> Korean characters are not properly encoded. "~~~" part was Korean
> letters.
Right, I only tested it with Latin-1 (where it does work).
Does this work for you?
(defun jh-broken-ms-encoding (param value)
(concat param "=\"" (rfc2047-encode-string value) "\""))
(defalias 'mail-header-encode-parameter 'jh-broken-ms-encoding)
next prev parent reply other threads:[~2002-05-02 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 3:16 Fail to encode attachement " Jinhyok Heo
2002-04-30 13:33 ` Jesper Harder
2002-05-02 0:56 ` Jinhyok Heo
2002-05-02 3:40 ` Jesper Harder
2002-05-02 9:04 ` Fail to encode attachment " Jinhyok Heo
2002-05-02 18:18 ` Jesper Harder [this message]
2002-05-05 23:55 ` Jinhyok Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m33cxabehn.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).