From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: rms@gnu.org, ding@gnus.org, emacs-devel@gnu.org,
tomas@tuxteam.de, monnier@iro.umontreal.ca, miles@gnu.org
Subject: Re: gnus should accept UTF8 even if UTF-8 is standard
Date: Tue, 21 Oct 2008 14:40:03 +0200 [thread overview]
Message-ID: <uabcyglzw.fsf@gnu.org> (raw)
In-Reply-To: <87k5c2tan9.fsf@xemacs.org>
> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Cc: rms@gnu.org,
> ding@gnus.org,
> emacs-devel@gnu.org,
> tomas@tuxteam.de,
> monnier@iro.umontreal.ca,
> miles@gnu.org
> Date: Tue, 21 Oct 2008 21:06:50 +0900
>
> Eli Zaretskii writes:
>
> > > > That implies that the return value would be a string, not the coding
> > > > system itself. I suggest we return the coding system (or nil), not
> > > > just the name.
> > >
> > > The coding system *is* just a name
> >
> > Not in GNU Emacs; see the doc string of `define-coding-system' (in
> > Emacs 23) or `make-coding-system' (in Emacs 22).
>
> If that's true, it's a shame; AFAICS there is no real utility to
> exposing the coding system object to Lisp
Emacs does not expose coding systems to Lisp. A coding system is a
just a symbol with special attributes, as far as Lisp is concerned.
This must be a misunderstanding of some kind, because I'm sure we are
talking about something we both understand. Let me take a step back
and explain what I meant in my original message:
> > Perhaps something like `canonicalize-coding-system-name' would be good.
>
> That implies that the return value would be a string, not the coding
> system itself. I suggest we return the coding system (or nil), not
> just the name.
What I meant is that, instead of returning a _string_, which is the
name of a coding system, it is better to return a _symbol_ of that
coding system. This will avoid the need to `intern' that string,
which is a gratuitous nuisance, because the function we are discussing
will most probably need to `intern' the string itself, for doing its
job.
I'm sure we both understand the difference between a thing and its
name, so vividly explained by Luis Carrol ;-)
> "utf8" is not a MIME charset (and no form of UTF-8 is an Emacs
> charset), but "utf-8" is an IANA-registered MIME charset.
Yes.
> AIUI, the point of the function is to guess what people who don't
> know what they're doing are trying to express (and to provide some
> interactive convenience to people who do know what they're doing).
Agreed, but in most cases the argument will be a valid MIME charset.
The case of "UTF8" is an exception. And even in this exceptional
case, I understand that "UTF8" came from some charset= header. That
is why I suggested coding-system-for-charset. I don't mind
coding-system-for-mime-charset, either, if that was your point. (In
Emacs 23+, the original Mule meaning of "charset" will fade out.)
next prev parent reply other threads:[~2008-10-21 12:40 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 20:30 jidanni
2008-10-14 20:50 ` Ted Zlatanov
2008-10-15 0:39 ` Kenichi Handa
2008-10-15 16:10 ` Richard M. Stallman
2008-10-15 17:32 ` Ted Zlatanov
2008-10-15 19:49 ` Reiner Steib
2008-10-15 19:05 ` Ted Zlatanov
2008-10-15 22:03 ` Reiner Steib
2008-10-15 21:23 ` Ted Zlatanov
2008-10-16 0:15 ` Katsumi Yamaoka
2008-10-20 16:23 ` Reiner Steib
2008-10-21 0:01 ` Katsumi Yamaoka
2008-12-15 23:35 ` Katsumi Yamaoka
2008-10-16 4:32 ` Stephen J. Turnbull
2008-10-16 6:47 ` Eli Zaretskii
2008-10-16 13:01 ` Ted Zlatanov
2008-10-16 2:41 ` Stefan Monnier
2008-10-16 14:27 ` Richard M. Stallman
2008-10-16 15:41 ` Stefan Monnier
2008-10-16 17:47 ` Eli Zaretskii
2008-10-17 19:59 ` Richard M. Stallman
2008-10-18 19:01 ` Stefan Monnier
2008-10-20 1:14 ` Richard M. Stallman
2008-10-20 3:21 ` Stefan Monnier
2008-10-20 8:42 ` Eli Zaretskii
2008-10-20 17:04 ` Richard M. Stallman
2008-10-21 4:39 ` Stephen J. Turnbull
2008-10-21 5:23 ` Miles Bader
2008-10-21 6:25 ` tomas
2008-10-21 6:21 ` Miles Bader
2008-10-21 7:44 ` tomas
2008-10-21 8:15 ` Eli Zaretskii
2008-10-21 9:06 ` Stephen J. Turnbull
2008-10-21 10:22 ` Eli Zaretskii
2008-10-21 12:06 ` Stephen J. Turnbull
2008-10-21 12:40 ` Eli Zaretskii [this message]
2008-10-22 2:34 ` Stephen J. Turnbull
2008-10-22 4:33 ` Eli Zaretskii
2008-10-22 21:02 ` Richard M. Stallman
2008-10-22 0:32 ` Kenichi Handa
2008-10-22 4:27 ` Eli Zaretskii
2009-01-27 4:51 ` Kenichi Handa
2008-10-21 8:06 ` Stephen J. Turnbull
2008-10-20 16:00 ` Reiner Steib
2008-10-20 22:03 ` Richard M. Stallman
2008-10-21 2:50 ` Kenichi Handa
2008-10-21 16:00 ` Ted Zlatanov
2008-10-22 1:22 ` Kenichi Handa
2008-10-22 2:07 ` Stephen J. Turnbull
2008-10-22 6:21 ` Richard M. Stallman
2008-10-23 2:34 ` Kenichi Handa
2008-10-23 21:08 ` Richard M. Stallman
2008-10-24 0:54 ` Kenichi Handa
2008-10-24 18:36 ` Richard M. Stallman
2008-10-22 13:15 ` Stefan Monnier
2008-10-24 17:21 ` Ted Zlatanov
2008-10-25 2:01 ` Richard M. Stallman
2008-10-25 2:32 ` Kenichi Handa
2008-10-26 4:10 ` Richard M. Stallman
2008-10-31 6:33 ` Kenichi Handa
2008-10-31 7:24 ` Miles Bader
2008-10-31 19:31 ` Richard M. Stallman
2008-11-01 2:17 ` Kenichi Handa
2008-11-02 1:53 ` Richard M. Stallman
2008-11-07 7:15 ` Kenichi Handa
2008-11-07 17:04 ` Richard M. Stallman
2008-10-25 18:27 ` Stefan Monnier
2008-10-26 4:10 ` Richard M. Stallman
2008-10-31 21:29 ` Stefan Monnier
2008-11-10 5:43 ` Kenichi Handa
2008-11-10 15:01 ` Stefan Monnier
2008-10-16 1:12 ` 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=uabcyglzw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=stephen@xemacs.org \
--cc=tomas@tuxteam.de \
/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).