From: Eli Zaretskii <eliz@gnu.org>
To: handa@gnu.org (K. Handa)
Cc: rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: ucs-normalize and diacritics
Date: Fri, 03 Aug 2018 20:57:21 +0300 [thread overview]
Message-ID: <83r2jftjsu.fsf@gnu.org> (raw)
In-Reply-To: <877el7msxp.fsf@gnu.org> (handa@gnu.org)
> From: handa@gnu.org (K. Handa)
> Cc: rpluim@gmail.com, emacs-devel@gnu.org
> Date: Fri, 03 Aug 2018 23:21:54 +0900
>
> In article <838t5rph0r.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
>
> > I meanwhile removed tis620-2533 on master and made it an alias to
> > thai-iso8859-11. It looked to me that a difference of one character
> > doesn't justify to have another charset with peculiar traits which in
> > addition causes unintuitive behavior. Do you think that change is OK?
>
> I think it is not the right way. Currently,
>
> (encode-char #xa0 'tis620-2533) => nil
> (encode-char #xa0 'thai-iso8859-11) => 32
>
> But, your change results in:
>
> (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? OTOH, it is strange to have two charsets that are identical
except for one character.
> That unintuitive behavior you mentioned is just Emacs' fault, and can be
> fixed, for instance, by my previous patch.
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?
next prev parent reply other threads:[~2018-08-03 17:57 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 [this message]
2018-08-05 13:58 ` K. Handa
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r2jftjsu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).