From 95a033a2fb40eb29805d34f5324d53d2245b2307 Mon Sep 17 00:00:00 2001 From: Dave Love Date: Tue, 21 Oct 2003 11:47:19 +0000 Subject: [PATCH] (Font Selection): Remove obsolete info. --- lispref/display.texi | 22 ---------------------- 1 file changed, 22 deletions(-) diff --git a/lispref/display.texi b/lispref/display.texi index 391d3f4764e..f4f1255bf63 100644 --- a/lispref/display.texi +++ b/lispref/display.texi @@ -2076,28 +2076,6 @@ face attributes, as determined by face merging, specify most of the font choice, but not all. Part of the choice depends on what character it is. - For multibyte characters, typically each font covers only one -character set. So each character set (@pxref{Character Sets}) specifies -a registry and encoding to use, with the character set's -@code{x-charset-registry} property. Its value is a string containing -the registry and the encoding, with a dash between them: - -@example -(plist-get (charset-plist 'latin-iso8859-1) - 'x-charset-registry) - @result{} "ISO8859-1" -@end example - - Unibyte text does not have character sets, so displaying a unibyte -character takes the registry and encoding from the variable -@code{face-default-registry}. - -@defvar face-default-registry -This variable specifies which registry and encoding to use in choosing -fonts for unibyte characters. The value is initialized at Emacs startup -time from the font the user specified for Emacs. -@end defvar - If the face specifies a fontset name, that fontset determines a pattern for fonts of the given charset. If the face specifies a font family, a font pattern is constructed. -- 2.39.2