unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Cecilio Pardo <cpardo@imayhem.com>
To: 73730@debbugs.gnu.org
Subject: bug#73730: 31.0.50; Support for color fonts on MS-Windows
Date: Sun, 27 Oct 2024 16:44:13 +0100	[thread overview]
Message-ID: <1acdb215-fa90-46d8-8088-3f5374903f28@imayhem.com> (raw)
In-Reply-To: <86plnl8ydp.fsf@gnu.org>

> Could you perhaps try the 32-bit build with the latest win32 binaries
> that the HarfBuzz project itself provides from their Releases page?
> 
>    https://github.com/harfbuzz/harfbuzz/releases

I replaced libharfbuzz-0.dll with the one from version 10.0.1 (the 
latest one) and it just works, with and without DirectWrite, without 
rebulding Emacs with the new headers.

Besides the normal build with meson/cmake, I've seen this:

   There is also amalgamated source provided with HarfBuzz which reduces
   whole process of building HarfBuzz to g++ src/harfbuzz.cc
   -fno-exceptions but there is no guarantee provided with buildability 	
   and reliability of features you get.

I will take a look at that.








  parent reply	other threads:[~2024-10-27 15:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 11:16 bug#73730: 31.0.50; Support for color fonts on MS-Windows Cecilio Pardo
2024-10-10 13:08 ` Eli Zaretskii
2024-10-10 15:14   ` Cecilio Pardo
2024-10-10 16:33     ` Eli Zaretskii
2024-10-10 16:46       ` Cecilio Pardo
2024-10-15 22:18   ` Cecilio Pardo
2024-10-16 11:01     ` Eli Zaretskii
2024-10-16 11:32       ` Eli Zaretskii
2024-10-16 21:35       ` Cecilio Pardo
2024-10-17  6:21         ` Eli Zaretskii
2024-10-17 10:38           ` Cecilio Pardo
2024-10-20 13:35             ` Cecilio Pardo
2024-10-20 13:55               ` Eli Zaretskii
2024-10-22 22:14                 ` Cecilio Pardo
2024-10-23 10:03                   ` Eli Zaretskii
2024-10-23 14:17                     ` Cecilio Pardo
2024-10-23 17:53                       ` Eli Zaretskii
2024-10-24 20:19                         ` Cecilio Pardo
2024-10-25  7:26                           ` Eli Zaretskii
2024-10-25 10:17                             ` Cecilio Pardo
2024-10-25 12:00                               ` Eli Zaretskii
2024-10-26 20:13                                 ` Cecilio Pardo
2024-10-27  6:36                                   ` Eli Zaretskii
2024-10-27 13:32                                     ` Eli Zaretskii
2024-10-27 13:41                                       ` Cecilio Pardo
2024-10-27 15:44                                       ` Cecilio Pardo [this message]
2024-10-27 16:54                                         ` Eli Zaretskii
2024-10-27 17:50                                           ` Cecilio Pardo
2024-10-27 19:15                                             ` Eli Zaretskii
2024-10-29  8:57                                               ` Cecilio Pardo
2024-10-25 11:51                           ` Eli Zaretskii
2024-10-25 13:43                             ` Cecilio Pardo
2024-10-20 16:17               ` Eli Zaretskii
2024-10-20 18:20                 ` Cecilio Pardo
2024-10-20 18:33                   ` Eli Zaretskii
2024-10-20 18:37                     ` Cecilio Pardo
2024-10-10 21:50 ` Cecilio Pardo
2024-10-11  3:36   ` Eli Zaretskii
2024-10-11  6:28     ` Eli Zaretskii
2024-10-11  7:19       ` Cecilio Pardo

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=1acdb215-fa90-46d8-8088-3f5374903f28@imayhem.com \
    --to=cpardo@imayhem.com \
    --cc=73730@debbugs.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).