From: Stephen Eglen <sje30@cam.ac.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 45557@debbugs.gnu.org, sje30@cam.ac.uk
Subject: bug#45557: 27.1; Incorrect rendering of COMBINING OVERLINE
Date: Thu, 31 Dec 2020 16:11:46 +0000 [thread overview]
Message-ID: <87mtxux8e5.fsf@cam.ac.uk> (raw)
In-Reply-To: <83r1n6gg7m.fsf@gnu.org>
> And the same info about "x" also shows the same font, i.e.
>
> ftcrhb:-UKWN-JuliaMono-normal-normal-normal-*-19-*-*-*-m-0-iso10646-1
>
> Anyway, the above means Emacs didn't compose these COMBINING OVERLINE
> woth "x", for some reason. The question is why.
yes; this is the output for "x":
position: 85 of 87 (97%), column: 2
character: x (displayed as x) (codepoint 120, #o170, #x78)
charset: ascii (ASCII (ISO646 IRV))
code point in charset: 0x78
script: latin
syntax: w which means: word
category: .:Base, L:Left-to-right (strong), a:ASCII, l:Latin, r:Roman
to input: type "C-x 8 RET 78" or "C-x 8 RET LATIN SMALL LETTER X"
buffer code: #x78
file code: #x78 (encoded by coding system utf-8-unix)
display: by this font (glyph code)
ftcrhb:-UKWN-JuliaMono-normal-normal-normal-*-19-*-*-*-m-0-iso10646-1 (#xA7)
Character code properties: customize what to show
name: LATIN SMALL LETTER X
general-category: Ll (Letter, Lowercase)
decomposition: (120) ('x')
There are text properties here:
fontified t
[back]
next prev parent reply other threads:[~2020-12-31 16:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 13:42 bug#45557: 27.1; Incorrect rendering of COMBINING OVERLINE Stephen Eglen
2020-12-31 5:24 ` Lars Ingebrigtsen
2020-12-31 7:33 ` Eli Zaretskii
2020-12-31 9:06 ` Stephen Eglen
2020-12-31 14:15 ` Eli Zaretskii
2020-12-31 13:45 ` Eli Zaretskii
2020-12-31 14:12 ` Stephen Eglen
2020-12-31 15:14 ` Eli Zaretskii
2020-12-31 16:11 ` Stephen Eglen [this message]
2021-01-01 8:28 ` Stephen Eglen
2021-01-01 11:09 ` Lars Ingebrigtsen
2021-01-02 18:47 ` James Cloos
2021-01-06 2:38 ` Madhu
2021-01-06 15:10 ` Eli Zaretskii
2021-01-06 16:00 ` Madhu
2021-01-06 16:10 ` Eli Zaretskii
2021-01-07 6:10 ` Madhu
2021-01-07 14:16 ` Eli Zaretskii
2021-01-07 15:28 ` Robert Pluim
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=87mtxux8e5.fsf@cam.ac.uk \
--to=sje30@cam.ac.uk \
--cc=45557@debbugs.gnu.org \
--cc=eliz@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).