unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: James Cloos <cloos@jhcloos.com>
Cc: larsi@gnus.org, rpluim@gmail.com, 39554@debbugs.gnu.org
Subject: bug#39554: 27.0.50; cairo not composing sequences
Date: Sat, 12 Feb 2022 08:50:27 +0200	[thread overview]
Message-ID: <83iltkshn0.fsf@gnu.org> (raw)
In-Reply-To: <m3o83d9lxo.fsf@carbon.jhcloos.org> (message from James Cloos on Fri, 11 Feb 2022 15:40:19 -0500)

> From: James Cloos <cloos@jhcloos.com>
> Date: Fri, 11 Feb 2022 15:40:19 -0500
> Cc: Robert Pluim <rpluim@gmail.com>, 39554@debbugs.gnu.org
> 
> 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.

_If_ it's a bug, it's either in the font or in HarfBuzz.  Not in Emacs.





  reply	other threads:[~2022-02-12  6:50 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
2022-02-12  6:50                       ` Eli Zaretskii [this message]
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=83iltkshn0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39554@debbugs.gnu.org \
    --cc=cloos@jhcloos.com \
    --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).