From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: ucs-normalize and diacritics Date: Fri, 03 Aug 2018 20:57:21 +0300 Message-ID: <83r2jftjsu.fsf@gnu.org> References: <877el7msxp.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1533318971 5933 195.159.176.226 (3 Aug 2018 17:56:11 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 3 Aug 2018 17:56:11 +0000 (UTC) Cc: rpluim@gmail.com, emacs-devel@gnu.org To: handa@gnu.org (K. Handa) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 03 19:56:07 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fleJ2-0001Oz-5z for ged-emacs-devel@m.gmane.org; Fri, 03 Aug 2018 19:56:04 +0200 Original-Received: from localhost ([::1]:52578 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fleL8-0005gS-Ux for ged-emacs-devel@m.gmane.org; Fri, 03 Aug 2018 13:58:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46736) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fleKY-0005gA-Vp for emacs-devel@gnu.org; Fri, 03 Aug 2018 13:57:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fleKY-0005qG-6K for emacs-devel@gnu.org; Fri, 03 Aug 2018 13:57:39 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:53576) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fleKR-0005nG-Km; Fri, 03 Aug 2018 13:57:31 -0400 Original-Received: from [176.228.60.248] (port=4549 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fleKQ-0007LJ-JY; Fri, 03 Aug 2018 13:57:31 -0400 In-reply-to: <877el7msxp.fsf@gnu.org> (handa@gnu.org) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:228132 Archived-At: > 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 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?