From: James Cloos <cloos@jhcloos.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Robert Pluim <rpluim@gmail.com>, 39554@debbugs.gnu.org
Subject: bug#39554: 27.0.50; cairo not composing sequences
Date: Fri, 11 Feb 2022 15:40:19 -0500 [thread overview]
Message-ID: <m3o83d9lxo.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <87v8xnche5.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 10 Feb 2022 08:25:38 +0100")
>>>>> "RP" == Robert Pluim <rpluim@gmail.com> writes:
>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
RP>> I donʼt see the issue with DejaVu Sans Mono in an Xft build, and can
RP>> reproduce it in an Xft+Harfbuzz build, so Cairo is not to blame here.
LI> in that case Emacs doesn't combine chars. So it's a
LI> matter of choosing a font that has wider coverage, I think.
no.
in this case one font is used.
w/ m17lib+libotf the two glyphs are combined and displayed one atop the other
(ie, z-axis stacking).
w/ harfbuzz the two glyphs still are combined but displayed next to each other.
(ie, x-axis stacking).
the first way is the correct way. the latter is a bug.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
next prev parent reply other threads:[~2022-02-11 20:40 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
2022-02-10 7:25 ` Lars Ingebrigtsen
2022-02-11 20:40 ` James Cloos [this message]
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=m3o83d9lxo.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=39554@debbugs.gnu.org \
--cc=larsi@gnus.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 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).