unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Eglen <sje30@cam.ac.uk>
Cc: larsi@gnus.org, 45557@debbugs.gnu.org, sje30@cam.ac.uk
Subject: bug#45557: 27.1; Incorrect rendering of COMBINING OVERLINE
Date: Thu, 31 Dec 2020 16:15:28 +0200	[thread overview]
Message-ID: <83y2hegiyn.fsf@gnu.org> (raw)
In-Reply-To: <87v9ci5ow6.fsf@cam.ac.uk> (message from Stephen Eglen on Thu, 31 Dec 2020 09:06:07 +0000)

> From: Stephen Eglen <sje30@cam.ac.uk>
> Cc: bug-gnu-emacs@gnu.org, Lars Ingebrigtsen <larsi@gnus.org>, Stephen Eglen
>  <sje30@cam.ac.uk>, 45557@debbugs.gnu.org
> Date: Thu, 31 Dec 2020 09:06:07 +0000
> 
> > Could be an issue with the version of HarfBuzz, perhaps?
> 
> $ pacman -Q harfbuzz
> 
> harfbuzz 2.7.2-1

Then I guess you should also look into Lars's guess: some of your
other font-related libraries, such as Freetype or Fontconfig.

What version of the offending font are you using?  I used the latest
released one available from their site.





  reply	other threads:[~2020-12-31 14:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30 13:42 bug#45557: 27.1; Incorrect rendering of COMBINING OVERLINE Stephen Eglen
2020-12-31  5:24 ` Lars Ingebrigtsen
2020-12-31  7:33   ` Eli Zaretskii
2020-12-31  9:06     ` Stephen Eglen
2020-12-31 14:15       ` Eli Zaretskii [this message]
2020-12-31 13:45 ` Eli Zaretskii
2020-12-31 14:12   ` Stephen Eglen
2020-12-31 15:14     ` Eli Zaretskii
2020-12-31 16:11       ` Stephen Eglen
2021-01-01  8:28       ` Stephen Eglen
2021-01-01 11:09         ` Lars Ingebrigtsen
2021-01-02 18:47         ` James Cloos
2021-01-06  2:38 ` Madhu
2021-01-06 15:10   ` Eli Zaretskii
2021-01-06 16:00     ` Madhu
2021-01-06 16:10       ` Eli Zaretskii
2021-01-07  6:10         ` Madhu
2021-01-07 14:16           ` Eli Zaretskii
2021-01-07 15:28             ` Robert Pluim

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=83y2hegiyn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45557@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=sje30@cam.ac.uk \
    /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).