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: Tue, 31 Jul 2018 21:37:40 +0900 [thread overview]
Message-ID: <87muu7h97v.fsf@gnu.org> (raw)
In-Reply-To: <83zhydrwoh.fsf@gnu.org> (message from Eli Zaretskii on Fri, 27 Jul 2018 09:59:26 +0300)
In article <83zhydrwoh.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> > > - It doesn't show this for the whole range 0200 to 0377, only for 0240
> > > to 0377, eg for 0200:
> >
> > That's a bug, somewhere. I will look into it when I have time.
> Not a bug, an unintended consequence of how we set up charsets. Now
> fixed on the emacs-26 branch.
> I wonder whether we can mark tis620-2533 a :supplementary-p charset.
> Kenichi, do you envision any problems that could be caused by that?
If we put :supplementary-p t to tis620-2533, M-x list-character-sets
lists that charset under "Supplementary Character Sets" section, which
will surprise tis620-2533 users (I think there are still many).
And, anyway, that change won't change the behavior of char-charset used
by describe-char. I have not yet read all mails in this thread, but if
the problem is that describe-char does not show eight-bit as a charset
of eight-bit characters, perhaps the best way is to modify describe-char
as this.
diff --git a/lisp/descr-text.el b/lisp/descr-text.el
index d8f8188eb1..aea090b907 100644
--- a/lisp/descr-text.el
+++ b/lisp/descr-text.el
@@ -403,6 +403,7 @@ describe-char
(eight-bit-p (and (not enable-multibyte-characters) (>= char 128)))
(charset (if eight-bit-p 'eight-bit
(or (get-text-property pos 'charset)
+ (and (encode-char char 'eight-bit) 'eight-bit)
(char-charset char))))
(composition (find-composition pos nil nil t))
(component-chars nil)
---
K. Handa
handa@gnu.org
next prev parent reply other threads:[~2018-07-31 12:37 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 [this message]
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
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=87muu7h97v.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.