From: handa@gnu.org (K. Handa)
To: Eli Zaretskii <eliz@gnu.org>
Cc: rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: ucs-normalize and diacritics
Date: Sun, 05 Aug 2018 22:58:43 +0900 [thread overview]
Message-ID: <871sbcncdo.fsf@gnu.org> (raw)
In-Reply-To: <83r2jftjsu.fsf@gnu.org> (message from Eli Zaretskii on Fri, 03 Aug 2018 20:57:21 +0300)
In article <83r2jftjsu.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> > (encode-char #xa0 'tis620-2533) => 32
> >
> > which is simply wrong.
> How important is that discrepancy? After all, tis620-2533 doesn't
> have the #xa0 character, so the situation above should never happen,
> right?
?? It happend when I wrote the code above. How can you tell that
no one try the same thing?
> OTOH, it is strange to have two charsets that are identical
> except for one character.
However strange it is, it is the fact that those two chararcter sets are
different at that point. Please see this page:
https://en.wikipedia.org/wiki/Thai_Industrial_Standard_620-2533
> Yes, it could be fixed, but why do we need to jump through hoops to
> keep one more charset, when we already have a charset that is
> identical to it except for one character?
The reason of having tis620-2533 was that it was added before
iso-8859-11. And, there have been no positive reason of deleting
tis620-2533 even after we added iso-8859-11. It is better to completely
drop the support of tis620-2533 (i.e. do not keep it as an alias for
iso-8859-11) than make Emacs tell a lie, but I think it is much better
to modify describe-char.
---
K. Handa
handa@gnu.org
next prev parent reply other threads:[~2018-08-05 13:58 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 18:17 ucs-normalize and diacritics Robert Pluim
2018-07-24 19:07 ` Eli Zaretskii
2018-07-24 19:20 ` Eli Zaretskii
2018-07-24 20:48 ` Robert Pluim
2018-07-25 2:32 ` Eli Zaretskii
2018-07-25 7:40 ` Robert Pluim
2018-07-25 14:39 ` Eli Zaretskii
2018-07-25 19:59 ` Robert Pluim
2018-07-26 19:47 ` Eli Zaretskii
2018-07-25 14:45 ` Robert Pluim
2018-07-25 14:57 ` Eli Zaretskii
2018-07-26 1:14 ` Richard Stallman
2018-07-26 14:15 ` Matt Lavallee
2018-07-26 18:42 ` Eli Zaretskii
2018-07-26 21:01 ` John Hsieh
2018-07-26 21:54 ` Stefan Monnier
2018-07-28 3:17 ` Richard Stallman
2018-07-31 1:09 ` John Hsieh
2018-07-31 15:22 ` Eli Zaretskii
2018-07-31 15:27 ` John Hsieh
2018-07-31 15:45 ` John Hsieh
2018-07-31 16:33 ` Eli Zaretskii
2018-07-31 16:28 ` Eli Zaretskii
2018-07-31 16:30 ` John Hsieh
2018-07-27 3:21 ` Richard Stallman
2018-07-27 23:48 ` John Hsieh
2018-07-26 8:40 ` Robert Pluim
2018-07-26 18:41 ` Eli Zaretskii
2018-07-26 20:40 ` Robert Pluim
2018-07-27 5:56 ` Eli Zaretskii
2018-07-27 6:59 ` Eli Zaretskii
2018-07-27 8:36 ` Robert Pluim
2018-07-31 12:37 ` K. Handa
2018-07-31 15:21 ` Eli Zaretskii
2018-08-03 14:21 ` K. Handa
2018-08-03 14:44 ` Andreas Schwab
2018-08-05 13:22 ` K. Handa
2018-08-05 15:28 ` Eli Zaretskii
2018-08-06 22:49 ` K. Handa
2018-08-11 8:20 ` Eli Zaretskii
2018-08-03 17:57 ` Eli Zaretskii
2018-08-05 13:58 ` K. Handa [this message]
2018-07-24 20:54 ` Robert Pluim
2018-07-25 2:36 ` Eli Zaretskii
2018-07-25 14:36 ` Eli Zaretskii
2018-07-25 20:11 ` Robert Pluim
2018-07-25 20:21 ` Cesar Crusius
2018-07-25 20:44 ` Robert Pluim
2018-07-25 22:59 ` Cesar Crusius
2018-07-26 8:14 ` Robert Pluim
2018-07-25 21:01 ` Yuri Khan
2018-07-26 2:41 ` Eli Zaretskii
2018-07-26 2:39 ` Eli Zaretskii
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=871sbcncdo.fsf@gnu.org \
--to=handa@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.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.
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.