From: Kenichi Handa <handa@m17n.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: gnus doesn't encode non-ascii attachment filenames
Date: Tue, 14 Feb 2006 11:13:00 +0900 [thread overview]
Message-ID: <E1F8pga-0007BC-00@etlken> (raw)
In-Reply-To: <87irriras8.fsf@emacsfans.org> (message from Zhang Wei on Tue, 14 Feb 2006 09:25:59 +0800)
In article <87irriras8.fsf@emacsfans.org>, Zhang Wei <id.brep@gmail.com> writes:
[...]
> Sorry, false alarm. This bug is only with the emacs-unicode-2
> branch. No problem with emacs 22.
> The difference of internal character representation between emacs23
> and emacs22, makes gnus can't handle non-ascii attachment filename
> correctly.
> To generate a rfc2231 encoded filename such as "%d6%d0%ce%c4",
> function (following-char) returns "d6" for the first char of the
> filename "d6d0cec4" in emacs22, while in emacs23 this function returns
> "3fffd6".
Ah, I see.
> This is an ugly hack to solve this problem:
For Emacs 23, we can have a better/simpler fix. But, could
someone tell me the maintenance policy of Gnus codes?
Should we modify codes in cvs HEAD so that it works also
with emacs-unicode-2 (perhaps with version check here and
there)? Or, should we directly modify codes in cvs
emacs-unicode-2?
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2006-02-14 2:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 7:00 gnus doesn't encode non-ascii attachment filenames Zhang Wei
[not found] ` <E1F8oEg-0007Q6-Vf@fencepost.gnu.org>
2006-02-14 1:25 ` Zhang Wei
2006-02-14 2:13 ` Kenichi Handa [this message]
2006-02-14 3:36 ` Miles Bader
2006-02-14 10:59 ` Gnus compatibility with Emacs 23 (unicode branch) (was: gnus doesn't encode non-ascii attachment filenames) Reiner Steib
2006-02-23 21:03 ` Gnus compatibility with Emacs 23 (unicode branch) Reiner Steib
2006-03-23 5:58 ` gnus doesn't encode non-ascii attachment filenames Kenichi Handa
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=E1F8pga-0007BC-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.