From: Eli Zaretskii <eliz@gnu.org>
To: stephen_leake@stephe-leake.org
Cc: emacs-devel@gnu.org
Subject: Re: bad default font on Windows mingw64
Date: Thu, 25 Jul 2019 19:51:47 +0300 [thread overview]
Message-ID: <837e86njks.fsf@gnu.org> (raw)
In-Reply-To: <83sgqxpjc2.fsf@gnu.org> (message from Eli Zaretskii on Tue, 23 Jul 2019 05:37:17 +0300)
> Date: Tue, 23 Jul 2019 05:37:17 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
>
> > From: Stephen Leake <stephen_leake@stephe-leake.org>
> > Date: Mon, 22 Jul 2019 18:03:29 -0700
> >
> > > pacman -Qi mingw-w64-x86_64-harfbuzz
> >
> > I had to do 'pacman -S --refresh' first, but now that's updated.
> >
> > Emacs 'make' did not notice the change, so I had to to 'make clean' first
> >
> > And now it works properly, so the problem was an old harbuzz library.
> >
> > Perhaps configure should check for that?
>
> I wouldn't know what check to insert. hb_font_get_nominal_glyph
> appeared in HarfBuzz 1.2.3, and we already check for that. I suspect
> your problem was actually with Freetype, which is HarfBuzz's
> dependency.
I asked on the HarfBuzz mailing list, and it turned out that our code
implicitly assumed HarfBuzz 2.0.0 or later, by omitting a function
call which was needed before that version. I've now added that call,
so we can indeed support old HarfBuzz versions on MS-Windows, per the
configure-time tests.
Thanks.
prev parent reply other threads:[~2019-07-25 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 17:02 bad default font on Windows mingw64 Stephen Leake
2019-07-22 17:43 ` Eli Zaretskii
2019-07-22 19:13 ` Stephen Leake
2019-07-22 19:35 ` Eli Zaretskii
2019-07-22 22:10 ` Stephen Leake
2019-07-22 22:58 ` Óscar Fuentes
2019-07-23 1:03 ` Stephen Leake
2019-07-23 2:37 ` Eli Zaretskii
2019-07-25 16:51 ` Eli Zaretskii [this message]
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=837e86njks.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen_leake@stephe-leake.org \
/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).