From: Robert Pluim <rpluim@gmail.com>
To: James Cloos <cloos@jhcloos.com>
Cc: 39554@debbugs.gnu.org
Subject: bug#39554: 27.0.50; cairo not composing sequences
Date: Fri, 14 Feb 2020 09:44:24 +0100 [thread overview]
Message-ID: <m2lfp5immv.fsf@gmail.com> (raw)
In-Reply-To: <m3k14pai1g.fsf@carbon.jhcloos.org> (James Cloos's message of "Thu, 13 Feb 2020 23:50:51 -0500")
>>>>> On Thu, 13 Feb 2020 23:50:51 -0500, James Cloos <cloos@jhcloos.com> said:
>>>>> "YM" == YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> writes:
YM> I guess the difference comes from with vs. without HarfBuzz rather
YM> than cairo vs. xft.
James> makes sense.
YM> Could you check if that is the case on your environment?
James> all i know is that w/o cairo, describe-char reports:
James> xft:-unknown-DejaVu Sans Mono-normal-normal-normal-*-22-*-*-*-m-0-iso10646-1
James> by these glyphs:
James> [0 1 48 19 13 0 13 17 1 nil]
James> [0 1 824 704 0 0 13 17 1 [-13 0 0]]
Thatʼs XFT not using harfbuzz
James> and w/ cairo it reports:
James> ftcrhb:-unknown-DejaVu Serif-normal-normal-normal-*-22-*-*-*-*-0-iso10646-1
James> by these glyphs:
James> [0 1 48 19 14 1 12 16 0 nil]
James> [0 1 824 741 0 -17 -1 18 1 nil]
And this is Cairo using harfbuzz.
James> I presume that the '0 0 13 17 1 [-13 0 0]' vs '0 -17 -1 18 1 nil'
James> represents the failed overlay.
James> and that ftcrhb expands to freetype-cairo-harfbuzz.
James> it is a pain to dig deep w/o the left hand, but i can try w/ some
James> leading suggestions. i haven't looked at the src since before my last
James> stroke, much less since this one.
I donʼt see the issue with DejaVu Sans Mono in an Xft build, and
can reproduce it in an Xft+Harfbuzz build, so Cairo is not to blame
here.
Robert
next prev parent reply other threads:[~2020-02-14 8:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 20:53 bug#39554: 27.0.50; cairo not composing sequences James Cloos
2020-02-11 3:26 ` 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 [this message]
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=m2lfp5immv.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=39554@debbugs.gnu.org \
--cc=cloos@jhcloos.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 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).