procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Document font backends for Cairo and/or HarfBuzz

Browse source 
* doc/lispref/frames.texi (Font and Color Parameters): Mention xfthb, ftcr,
and ftcrhb font backends.
This commit is contained in:
YAMAMOTO Mitsuharu 2019-05-11 16:09:05 +09:00
parent bc991e4276
commit 5d7dafacf4
1 changed files with 11 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
doc/lispref/frames.texi
View file

@ -2279,12 +2279,17 @@ variable do not take effect immediately, only when you specify the
@item font-backend
A list of symbols, specifying the @dfn{font backends} to use for
drawing fonts in the frame, in order of priority. On X, there are
currently two available font backends: @code{x} (the X core font
driver) and @code{xft} (the Xft font driver). On MS-Windows, there are
currently two available font backends: @code{gdi} and
@code{uniscribe} (@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.
currently three available font backends if Emacs was built without the
Cairo drawing: @code{x} (the X core font driver), @code{xft} (the Xft
font driver), and @code{xfthb} (the Xft font driver with HarfBuzz text
shaping). If built with the Cairo drawing, then there are two
available font backends: @code{ftcr} (the FreeType font driver on
Cairo) and @code{ftcrhb} (the FreeType font driver on Cairo with
HarfBuzz text shaping). On MS-Windows, there are currently two
available font backends: @code{gdi} and @code{uniscribe}
(@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.
@vindex background-mode@r{, a frame parameter}
@item background-mode