From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71766-done@debbugs.gnu.org
Subject: bug#71766: 30.0.60; HarfBuzz is not used in the Cygwin-w32 build
Date: Tue, 25 Jun 2024 11:36:43 -0400 [thread overview]
Message-ID: <1655b8cf-fab5-4df8-9d36-d33513222cb9@cornell.edu> (raw)
In-Reply-To: <861q4lbvif.fsf@gnu.org>
On 6/24/2024 10:34 PM, Eli Zaretskii wrote:
>> Date: Mon, 24 Jun 2024 21:18:31 -0400
>> From: Ken Brown <kbrown@cornell.edu>
>>
>> The HarfBuzz library is hard-coded as libharfbuzz-0.dll in
>> w32uniscribe.c, but this is only valid on MS-Windows. On Cygwin the
>> library is cygharfbuzz-0.dll. As a result, HarfBuzz is not used in the
>> Cygwin-w32 build. The obvious fix is
>
> Please install this on the emacs-30 branch if it's all that is needed.
Done.
>> Before pushing this, I'd like to test it, but I don't know enough about
>> HarfBuzz to do that. Can someone tell me how to test that HarfBuzz is
>> actually being used as intended? All I've done so far is to start emacs
>> and note that the display looks reasonable.
>
> Type "C-u C-x =" on some character, it should tell you what is the
> backend (at the beginning of the font name). I would also use "C-h h"
> to compare the display with another configuration where you know
> HarfBuzz is being used.
Thanks, it looks good. Closing.
Ken
prev parent reply other threads:[~2024-06-25 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 1:18 bug#71766: 30.0.60; HarfBuzz is not used in the Cygwin-w32 build Ken Brown
2024-06-25 2:34 ` Eli Zaretskii
2024-06-25 15:36 ` Ken Brown [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=1655b8cf-fab5-4df8-9d36-d33513222cb9@cornell.edu \
--to=kbrown@cornell.edu \
--cc=71766-done@debbugs.gnu.org \
--cc=eliz@gnu.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).