unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 39554@debbugs.gnu.org, James Cloos <cloos@jhcloos.com>
Subject: bug#39554: 27.0.50; cairo not composing sequences
Date: Thu, 10 Feb 2022 08:25:38 +0100	[thread overview]
Message-ID: <87v8xnche5.fsf@gnus.org> (raw)
In-Reply-To: <m2lfp5immv.fsf@gmail.com> (Robert Pluim's message of "Fri, 14 Feb 2020 09:44:24 +0100")

Robert Pluim <rpluim@gmail.com> writes:

> 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.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

This looks very similar to the problem in bug#44784, and the issue there
was that Emacs was choosing a font for ̷ that's not the same as the font
used for 0 -- in that case Emacs doesn't combine chars.  So it's a
matter of choosing a font that has wider coverage, I think.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-02-10  7:25 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 [this message]
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=87v8xnche5.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=39554@debbugs.gnu.org \
    --cc=cloos@jhcloos.com \
    --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).