From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, 42256@debbugs.gnu.org
Subject: bug#42256: 27.0.50; composition
Date: Sun, 12 Jul 2020 02:57:03 +0300 [thread overview]
Message-ID: <87mu451uo8.fsf@mail.linkov.net> (raw)
In-Reply-To: <83mu47q48x.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Jul 2020 09:21:50 +0300")
>> But I wonder why display combining character names only on TTY frames?
>
> Because font glyphs have no names, at least not names that Emacs knows
> about and that could be of use to users.
Font glyphs have no names indeed, but the characters that they display
have names.
>> Composed with the following character(s) "́" using this font:
>> x:-misc-fixed-medium-r-normal--15-108-100-100-c-60-iso10646-1
>> by these glyphs:
>> [0 1 97 97 6 0 6 12 3 nil]
>> [0 1 769 769 6 0 6 12 3 [-6 0 0]]
>>
>> I don't know what these glyph numbers mean
>
> Which numbers? If you mean the components of the glyph vectors, see
> the doc string of composition-get-gstring. I don't think the details
> of this information is useful for casual users.
I agree that the details of the glyph vectors are not useful for users.
But the character names are hugely useful, even on GUI frames,
not only on TTY frames.
>> but still no combining character names are displayed on GUI frames.
>
> I don't think I understand what you mean by that.
The names of combining characters under point are now displayed on TTY frames,
but still not displayed on GUI frames. This information about buffer characters
is needed without relation to fonts and glyphs.
next prev parent reply other threads:[~2020-07-11 23:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 2:41 bug#42256: 27.0.50; composition Richard Stallman
2020-07-08 14:18 ` Eli Zaretskii
2020-07-09 3:01 ` Richard Stallman
2020-07-09 17:51 ` Eli Zaretskii
2020-07-09 23:36 ` Juri Linkov
2020-07-10 6:21 ` Eli Zaretskii
2020-07-11 2:17 ` Richard Stallman
2020-07-11 23:57 ` Juri Linkov [this message]
2020-07-12 15:40 ` Eli Zaretskii
2020-07-12 23:35 ` Juri Linkov
2020-07-13 3:37 ` Eli Zaretskii
2020-07-13 13:39 ` Eli Zaretskii
2020-07-14 0:13 ` Juri Linkov
2020-07-14 2:36 ` Eli Zaretskii
2020-07-14 23:20 ` Juri Linkov
2020-07-15 14:39 ` Eli Zaretskii
2020-07-15 23:43 ` Juri Linkov
2020-07-16 16:40 ` Eli Zaretskii
2020-07-13 2:56 ` Richard Stallman
2020-07-10 3:52 ` Richard Stallman
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=87mu451uo8.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=42256@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rms@gnu.org \
/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).