unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs 28: bitmap fonts, vector font character spacing
Date: Mon, 24 Jul 2023 19:14:38 +0300	[thread overview]
Message-ID: <83ttttqob5.fsf@gnu.org> (raw)
In-Reply-To: <871qgx72h7.fsf@drac> (message from Christoph Groth on Mon, 24 Jul 2023 17:28:52 +0200)

> From: Christoph Groth <christoph@grothesque.org>
> Date: Mon, 24 Jul 2023 17:28:52 +0200
> 
> Eli Zaretskii wrote:
> > 
> > Basically, Cairo dropped support for bitmap fonts.  So I'd expect them
> > not to work at all in an Emacs built with Cairo.
> 
> Thanks for the quick clarification!  Perhaps that NEWS entry could be
> reformulated to be more categorical?  “Some problems” sounded to me like
> there could be ways to work around the problem, and I wasted too much
> time trying to find one.  (As strange as it sounds, after staring at
> Terminus for a couple of hours on most days for many years I grew
> attached to it...)

We actually said that, but in NEWS shipped with Emacs 27:

  ** The configure option '--with-cairo' is no longer experimental.
  This builds Emacs with Cairo drawing, and supports built-in printing
  when Emacs is built with GTK+.  Some severe bugs in this build were
  fixed, and we can therefore offer this to users without caveats.  Note
  that building with Cairo enabled results in using Pango instead of
  libXft for font support, and that Pango 1.44 has removed support for
  bitmapped fonts.



  parent reply	other threads:[~2023-07-24 16:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24 15:28 Emacs 28: bitmap fonts, vector font character spacing Christoph Groth
2023-07-24 15:37 ` Robert Pluim
2023-07-24 16:14 ` Eli Zaretskii [this message]
2023-08-10 11:28 ` Gregory Heytings
2023-08-10 14:53   ` Emanuel Berg
  -- strict thread matches above, loose matches on Subject: below --
2023-07-25 11:12 Christoph Groth
2023-07-24 16:10 Christoph Groth
2023-07-24 16:29 ` PierGianLuca
2023-07-24 13:15 Christoph Groth
2023-07-24 13:45 ` Eli Zaretskii
2023-07-24 13:56 ` PierGianLuca
2023-07-24 14:41   ` Hongyi Zhao
2023-07-25  9:49 ` Manuel Giraud via Users list for the GNU Emacs text editor
2023-07-27  8:37 ` PierGianLuca

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=83ttttqob5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).