From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Mime types and attached files
Date: Mon, 17 Apr 2006 10:54:59 +0900 [thread overview]
Message-ID: <b4md5fhq83w.fsf@jpl.org> (raw)
In-Reply-To: <m3bqv49thn.fsf@quimbies.gnus.org>
>>>>> In <m3bqv49thn.fsf@quimbies.gnus.org>
>>>>> Lars Magne Ingebrigtsen wrote:
> Fabrice Popineau <Fabrice.Popineau@supelec.fr> writes:
>> I have send an email with an msword (sorry!) file attached. The file
>> name has non ascii chars and it was sent using these lines:
>>
>> --=-=-=
>> Content-Type: application/msword
>> Content-Disposition: attachment;
>> filename*=iso-8859-1''IIC%20p79%20%e0%2089%20-%202005.DOC
> Gnus uses RFC2231 encoding for non-ascii text in the MIME parameters,
> which is, er, correct. However, it's unusual.
> I'm sort of leaning towards switching over to using quoted-printable
> here instead of RFC2231 to get interoperability with... a lot of the
> world.
Yes, most of Windoze mailers don't support RFC2231. Instead,
they use the complacent RFC2047-like encoding. Gnus can decode
both styles of encoded file names. That's good. However, I
must evaluate the form[1]
(defalias 'mail-header-encode-parameter 'rfc2047-encode-parameter)
when sending files with Japanese names in business. That's very
annoying, though I never want to make it the default (so, I
restore it into `rfc2231-encode-string' after sending a mail).
> Does Thunderbird understand RFC2231, for instance?
Yes, it does. However, the encoder has a bug[2] in the released
version.
[1] (info "(emacs-mime)rfc2047")
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=323318
next prev parent reply other threads:[~2006-04-17 1:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 20:43 Fabrice Popineau
2006-04-14 13:28 ` Lars Magne Ingebrigtsen
2006-04-17 1:54 ` Katsumi Yamaoka [this message]
2006-04-17 9:04 ` Lars Magne Ingebrigtsen
2006-04-17 10:15 ` Katsumi Yamaoka
2006-04-17 11:12 ` Lars Magne Ingebrigtsen
2006-04-17 11:40 ` gdt
2006-04-17 12:32 ` Lars Magne Ingebrigtsen
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=b4md5fhq83w.fsf@jpl.org \
--to=yamaoka@jpl.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).