[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
emacs-27 7e37e61: Correct statement about ftcr and recommend HarfBuzz
From: |
Robert Pluim |
Subject: |
emacs-27 7e37e61: Correct statement about ftcr and recommend HarfBuzz |
Date: |
Tue, 21 Jan 2020 12:21:20 -0500 (EST) |
branch: emacs-27
commit 7e37e61f4b9729ac54d80715de9dcc928e0aaf26
Author: Robert Pluim <address@hidden>
Commit: Robert Pluim <address@hidden>
Correct statement about ftcr and recommend HarfBuzz
* doc/lispref/frames.texi (Font and Color Parameters): Correct
statement about availability of ftcr in the presence of HarfBuzz.
Recommend HarfBuzz.
---
doc/lispref/frames.texi | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/doc/lispref/frames.texi b/doc/lispref/frames.texi
index 0c42ebf..d855ecc 100644
--- a/doc/lispref/frames.texi
+++ b/doc/lispref/frames.texi
@@ -2300,17 +2300,17 @@ available font backends: @code{x} (the X core font
driver), @code{xft}
HarfBuzz text shaping). If built with Cairo drawing, there are also
three potentially available font backends on X: @code{x}, @code{ftcr}
(the FreeType font driver on Cairo), and @code{ftcrhb} (the FreeType
-font driver on Cairo with HarfBuzz text shaping). Note that the
-@code{ftcr} and @code{ftcrhb} drivers are mutually exclusive (and
-similarly for @code{xft} and @code{xfthb}), with the choice being made
-at build time. On MS-Windows, there are currently three available
-font backends: @code{gdi} (the core MS-Windows font driver),
-@code{uniscribe} (font driver for OTF and TTF fonts with text shaping
-by the Uniscribe engine), and @code{harfbuzz} (font driver for OTF and
-TTF fonts with HarfBuzz text shaping) (@pxref{Windows Fonts,,, emacs,
-The GNU Emacs Manual}). On other systems, there is only one available
-font backend, so it does not make sense to modify this frame
-parameter.
+font driver on Cairo with HarfBuzz text shaping). When Emacs is built
+with HarfBuzz, the default font driver is @code{ftcrhb}, although use
+of the @code{ftcr} driver is still possible, but not recommended. On
+MS-Windows, there are currently three available font backends:
+@code{gdi} (the core MS-Windows font driver), @code{uniscribe} (font
+driver for OTF and TTF fonts with text shaping by the Uniscribe
+engine), and @code{harfbuzz} (font driver for OTF and TTF fonts with
+HarfBuzz text shaping) (@pxref{Windows Fonts,,, emacs, The GNU Emacs
+Manual}). The @code{harfbuzz} driver is similarly recommended. On
+other systems, there is only one available font backend, so it does
+not make sense to modify this frame parameter.
@vindex background-mode@r{, a frame parameter}
@item background-mode
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- emacs-27 7e37e61: Correct statement about ftcr and recommend HarfBuzz,
Robert Pluim <=