From: Jinhyok Heo <novembre+dated+1020567757.8c22a8@ournature.org>
Subject: Fail to encode attachement filenames properly.
Date: Tue, 30 Apr 2002 12:16:14 +0900 [thread overview]
Message-ID: <microsoft-free.3oheltq3k1.fsf@ournature.org> (raw)
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=?="
`--------------------------------------------
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
`--------------------------------------------
Gnus seems to fail to encode filenames correctly.
--
| 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
next reply other threads:[~2002-04-30 3:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 3:16 Jinhyok Heo [this message]
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
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=microsoft-free.3oheltq3k1.fsf@ournature.org \
--to=novembre+dated+1020567757.8c22a8@ournature.org \
/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).