From: James Cloos <cloos@jhcloos.com>
To: 39554@debbugs.gnu.org
Subject: bug#39554: 27.0.50; cairo not composing sequences
Date: Mon, 10 Feb 2020 15:53:32 -0500 [thread overview]
Message-ID: <m37e0u6u5v.fsf@carbon.jhcloos.org> (raw)
Sequences like 0̸ fail to display composed in master --with-cairo but do
when usin xft.
In a version w/o cairo I get:
Composed with the following character(s) "̸" using this font:
xft:-unknown-DejaVu Sans Mono-normal-normal-normal-*-22-*-*-*-m-0-iso10646-1
by these glyphs:
and the single char takes up the same width as any ascii letter.
W/ cair i get:
Composed with the following character(s) "̸" using this font:
ftcrhb:-unknown-DejaVu Sans Mono-normal-normal-normal-*-22-*-*-*-m-0-iso10646-1
by these glyphs:
[0 1 48 19 13 1 12 16 0 nil]
[0 1 824 704 13 0 13 17 1 nil]
and the single char takes twice the expected width, but still works as a
sing;e char. OTOH, in the *Help* buffer '"̸"' is three separate chars.
Buth with xft '"̸"' displays with the slash overlaying the first ".
As it should.
The ftcrhb: code needs to display the combining chars over the base
chars like the earlier code does.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
next reply other threads:[~2020-02-10 20:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 20:53 James Cloos [this message]
2020-02-11 3:26 ` bug#39554: 27.0.50; cairo not composing sequences Eli Zaretskii
[not found] ` <m3d0ajd4fq.fsf@carbon.jhcloos.org>
2020-02-12 19:59 ` Eli Zaretskii
2020-02-13 20:16 ` James Cloos
2020-02-13 20:24 ` Eli Zaretskii
2020-02-14 0:58 ` James Cloos
2020-02-14 1:07 ` YAMAMOTO Mitsuharu
2020-02-14 4:50 ` James Cloos
2020-02-14 8:44 ` Robert Pluim
2022-02-10 7:25 ` Lars Ingebrigtsen
2022-02-11 20:40 ` James Cloos
2022-02-12 6:50 ` Eli Zaretskii
2022-02-11 20:48 ` James Cloos
2020-02-11 3:27 ` Eli Zaretskii
2020-02-12 18:54 ` James Cloos
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=m37e0u6u5v.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=39554@debbugs.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).