unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Inaccuracy in NEWS.28
Date: Tue, 01 Mar 2022 20:46:59 +0800	[thread overview]
Message-ID: <87tuch262k.fsf@yahoo.com> (raw)
In-Reply-To: <83o82pluym.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 01 Mar 2022 14:26:41 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> So if you think mentioning Pango there is incorrect (but please
> explain why, as I don't think I agree with your reasoning: AFAIK Pango
> is the text layout engine used by Cairo)

Pango is a text layout and font management library which operates on a
much higher level than cairo.  It performs bidirectional reordering, and
delegates to HarfBuzz for text shaping, along with using FreeType for
calculating glyph metrics and for opening fonts, and fontconfig to
enumerate fonts.

Cairo is one of the many libraries that Pango can use to display glyphs
onto the glass, but is otherwise unrelated to Pango.

However, judging by those discussions, there does seem to be some
problems with cairo and bitmap fonts.  So how about saying this instead:

  Building with Cairo is known to cause some problems with bitmap fonts.
  This may require you to adjust your font settings, or to build with
  Xft support instead.

Thanks.



  reply	other threads:[~2022-03-01 12:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87fso22ryu.fsf.ref@yahoo.com>
2022-03-01  4:54 ` Inaccuracy in NEWS.28 Po Lu
2022-03-01 12:26   ` Eli Zaretskii
2022-03-01 12:46     ` Po Lu [this message]
2022-03-01 13:14       ` Eli Zaretskii
2022-03-01 13:22         ` Po Lu
2022-03-01 13:47           ` Robert Pluim
2022-03-01 14:45             ` Eli Zaretskii
2022-03-02  0:56               ` Po Lu
2022-03-02  8:25                 ` Robert Pluim
2022-03-02  8:32                   ` Po Lu

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=87tuch262k.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).