From: "Miles Bader" <miles@gnu.org>
To: "Reiner Steib" <Reiner.Steib@gmx.de>,
"Miles Bader" <miles@gnu.org>,
ding@gnus.org
Subject: Re: Emacs unicode merge changes to Gnus
Date: Thu, 7 Feb 2008 07:44:36 +0900 [thread overview]
Message-ID: <fc339e4a0802061444g44ea69efu2657bab5bed42fa2@mail.gmail.com> (raw)
In-Reply-To: <v9prv9rb28.fsf@marauder.physik.uni-ulm.de>
> - (let ((coding-system-for-read gnus-ding-file-coding-system))
> - (gnus-load ding-file))
> + (gnus-load ding-file)
...
> - (princ ";; -*- emacs-lisp -*-\n")
> + (princ (format ";; -*- mode:emacs-lisp; coding: %s; -*-\n"
> + gnus-ding-file-coding-system))
...
> This could cause problems for people switching (from Emacs 23) to
> Emacs <= 22 (or XEmacs). AFAICS, Emacs 21 and 22 simply ignore the
> cookie if the coding is unknown. I'd expect problems for people using
> e.g. non-ASCII group names. Any ideas how to fix this problem?
It seems like this change wouldn't affect that case either way: if
they switch emacs to an old version, and gnus-ding-file-coding-system
is something unknown, and they actually have some non-ascii chars in
there, they're screwed, whether with the old code or the new code.
There's a case where the old code could work better, if the file is
written with utf-8-emacs (the default now, I guess), and the
switched-to-system happens to use a coding system of utf-8 which is
largely compatible; for Emacs 21, this won't happen (the switcher is
just plain screwed in this case, no matter what, I think), as Emacs 21
doesn't support utf-8.
Now, the new code could also work (more properly, instead of by
accident) in the switching-to-emacs-22 case, if Gnus used a coding:
tag of "utf-8" instead of "utf-8-emacs" when possible.
In any case, I think it definitely should always write a coding: tag,
and clearly using it is the way for the future. To handle the
switch-to-emacs-22 case, it could try to use "coding: utf-8" except
when that can't encode something. The only case I know of when
utf-8-emacs works but utf-8 doesn't, is when you have random binary
bytes embedded in the file, in which case I think the proper thing to
do is say "don't an idiot."
It seems to me that the switch-to-emacs-21 case is going to break no
matter what (unless you only use ascii), so there shouldn't be any
effort expended to fix it.
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2008-02-06 22:44 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 [this message]
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
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=fc339e4a0802061444g44ea69efu2657bab5bed42fa2@mail.gmail.com \
--to=miles@gnu.org \
--cc=Reiner.Steib@gmx.de \
--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).