From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: bugs@gnus.org, ding@gnus.org
Subject: Re: gnus doesn't encode non-ascii attachment filenames
Date: Wed, 15 Feb 2006 07:49:27 +0900 [thread overview]
Message-ID: <b4mbqx9tv2g.fsf@jpl.org> (raw)
In-Reply-To: <8764njdbxi.fsf@emacsfans.org>
>>>>> In <8764njdbxi.fsf@emacsfans.org> Zhang Wei wrote:
> While composing mail, if I attach a file with non-ascii(chinese
> actually) filename, it's failed to correctly encode the filename.
> --
> Zhang Wei or Brep
> <brep@smth.org>
How is it incorrect? Gnus does the RFC2231 encoding, that is
very correct. However, in fact, many mail softwares don't
understand it. They likely use the RFC2047-like encoding that
can understand only them. That has not been standardized. Gnus
can handle such an encoding, though.
Here's an extract from the Emacs MIME manual. Does it help?
`rfc2047-encode-parameter'
Encode a parameter in the RFC2047-like style. This is a
replacement for the `rfc2231-encode-string' function. *Note
rfc2231::.
When attaching files as MIME parts, we should use the RFC2231
encoding to specify the file names containing non-ASCII
characters. However, many mail softwares don't support it in
practice and recipients won't be able to extract files with
correct names. Instead, the RFC2047-like encoding is acceptable
generally. This function provides the very RFC2047-like encoding,
resigning to such a regrettable trend. To use it, put the
following line in your `~/.gnus.el' file:
(defalias 'mail-header-encode-parameter 'rfc2047-encode-parameter)
parent reply other threads:[~2006-02-14 22:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <8764njdbxi.fsf@emacsfans.org>]
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=b4mbqx9tv2g.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=bugs@gnus.org \
--cc=ding@gnus.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).