From: Miles Bader <miles.bader@necel.com>
To: ding@gnus.org
Subject: Re: Emacs unicode merge changes to Gnus
Date: Thu, 07 Feb 2008 19:24:03 +0900 [thread overview]
Message-ID: <buo3as5t67w.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <b4mzlud9l9h.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Oops. I confirmed they aren't cooked like group names. In
> addition, I realized what you pointed to. That is, even if
> `utf-8-emacs', that covers even byte-code, is the best choice
> for Emacs 23, it cannot be used as a coding cookie. Sorry for
> the noise.
What about (1) using the coding: cookie, (2) change the coding system
used to be utf-8 if possible (no binary), and utf-8-emacs otherwise.
That should more or less work correctly except when people have binary
junk, and that should be very rare (right...?).
I guess it won't work for some other cases, like someone with CJK text
who switches from Emacs 23 to Emacs 21, but ...
-Miles
--
`To alcohol! The cause of, and solution to,
all of life's problems' --Homer J. Simpson
next prev parent reply other threads:[~2008-02-07 10:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 2:30 Miles Bader
2008-02-06 22:10 ` Reiner Steib
2008-02-06 22:44 ` Miles Bader
2008-02-06 23:06 ` Reiner Steib
2008-02-06 23:22 ` Miles Bader
2008-02-06 23:27 ` Katsumi Yamaoka
2008-02-07 8:24 ` Reiner Steib
2008-02-07 9:19 ` Katsumi Yamaoka
2008-02-07 10:24 ` Miles Bader [this message]
2008-02-15 0:42 ` Miles Bader
2008-02-15 17:30 ` Reiner Steib
2008-02-15 21:59 ` Miles Bader
2008-02-16 0:39 ` Reiner Steib
2008-02-20 0:29 ` Miles Bader
2008-02-20 19:34 ` Reiner Steib
2008-02-26 21:17 ` Reiner Steib
2008-02-20 0:30 ` Miles Bader
2008-02-20 19:23 ` Reiner Steib
2008-02-23 18:07 ` Reiner Steib
2008-02-24 1:41 ` Miles Bader
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=buo3as5t67w.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--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).