[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
emacs-28 225e0d6047: Correct etc/NEWS entry about bitmapped fonts
From: |
Robert Pluim |
Subject: |
emacs-28 225e0d6047: Correct etc/NEWS entry about bitmapped fonts |
Date: |
Wed, 2 Mar 2022 03:24:51 -0500 (EST) |
branch: emacs-28
commit 225e0d6047de9576ee48ce612fcd561f818195aa
Author: Po Lu <luangruo@yahoo.com>
Commit: Robert Pluim <rpluim@gmail.com>
Correct etc/NEWS entry about bitmapped fonts
* etc/NEWS: Don't say that bitmap font issues are due to Pango, that's
not accurate.
---
etc/NEWS | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/etc/NEWS b/etc/NEWS
index 58c7c44a2b..84041d79c2 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -43,11 +43,10 @@ recommend examining any such warnings before you decide
they are
false.
** The Cairo graphics library is now used by default if present.
-'--with-cairo' is now the default, if the appropriate development files
-are found by 'configure'. Note that building with Cairo means using
-Pango instead of libXFT for font support. Since Pango 1.44 has
-removed support for bitmapped fonts, this may require you to adjust
-your font settings.
+'--with-cairo' is now the default, if the appropriate development
+files are found by 'configure'. 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.
Note also that 'FontBackend' settings in ".Xdefaults" or
".Xresources", or 'font-backend' frame parameter settings in your init
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- emacs-28 225e0d6047: Correct etc/NEWS entry about bitmapped fonts,
Robert Pluim <=