From: Kenichi Handa <handa@m17n.org>
To: rms@gnu.org
Cc: tzz@lifelogs.com, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: gnus should accept UTF8 even if UTF-8 is standard
Date: Sat, 01 Nov 2008 11:17:14 +0900 [thread overview]
Message-ID: <E1Kw638-0007Iz-Hk@etlken.m17n.org> (raw)
In-Reply-To: <E1KvziI-0005Qf-30@fencepost.gnu.org> (rms@gnu.org)
In article <E1KvziI-0005Qf-30@fencepost.gnu.org>, "Richard M. Stallman" <rms@gnu.org> writes:
> In the case of filenames, there surely exist the actual file
> with those ignored extensions. But, in the case of coding
> systems, such an alias as "utf8" doesn't exist. Or do you
> still propose to make such an alias as a sencond-class name
> in advance?
> To define them as second-class extensions would be one method.
> Another is this: `read-coding-system' could create the completion
> alist, then add to it modified entries made by replacing "utf-8" with
> "utf8". Then it could read the name, using the appropriate kind of
> completion. When it gets back the value from `completing-read', it
> could replace "utf8" with "utf-8".
> This avoids having a list of second-class "utf8" aliases. Those
> aliases would be constructed automatically from the valid names
> that start with "utf-8".
> If so, I strongly oppose to it.
> Why, what harm would it do?
With that, people think that "utf8" is a valid coding system
name, and will write a code something like this:
(decode-coding-string STR 'utf8)
and found that it signals an error because utf8 is not
statically declared as an alias.
> If we are
> going to allow users to type all names that are accepted by
> iconv, we must make so many aliases.
> I don't know which names are accepted by iconv, so I don't know
> whether I'm in favor of accepting them all.
> But suppose that we decide to accept them all, and suppose we decide
> to do it by defining each one as a second-class alias. How many
> second-class aliases would that require?
For instance, "% iconv -l", lists these variants for
iso-8859-1:
"ISO-8859-1", "ISO88591" "8859_1", "ISO_8859-1"
In addition, we must add (partial) lowercase versions.
Partial means something like this: Iso ISo isO
And, as we also have to add "-dos", "-unix", "-mac"
variatants.
So total aliases we'll add are more than 100 just for
iso-8859-1.
And, the "iconv" program actualy accepts any pattern
matching with "iso[^a-zA-Z0-9]8859-1"; e.g. "iso 8859-1",
"iso=8859-1", etc.
Considering them, it is not realistic to have all aliases
statically.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-11-01 2:17 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
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 [this message]
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=E1Kw638-0007Iz-Hk@etlken.m17n.org \
--to=handa@m17n.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=tzz@lifelogs.com \
/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).