unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: 10399@debbugs.gnu.org
Subject: bug#10399: [PATCH] Document win32 font backends
Date: Thu, 29 Dec 2011 06:06:16 -0800	[thread overview]
Message-ID: <24726464e3220fa8654e52357dfd56ab2d5bdb43.1325166907.git.dancol@dancol.org> (raw)

---
 doc/lispref/frames.texi |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/doc/lispref/frames.texi b/doc/lispref/frames.texi
index dad1f28..e4338c8 100644
--- a/doc/lispref/frames.texi
+++ b/doc/lispref/frames.texi
@@ -888,7 +888,10 @@ and bar becomes a narrower bar).
 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 other systems, there
+driver) and @code{xft} (the Xft font driver).  On Windows, there
+are currently two available font backends: @code{gdi} and
+@code{uniscribe}.
+On other systems, there
 is only one available font backend, so it does not make sense to
 modify this frame parameter.
 
-- 
1.7.5.1






             reply	other threads:[~2011-12-29 14:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-29 14:06 Daniel Colascione [this message]
2011-12-29 16:21 ` bug#10399: [PATCH] Document win32 font backends Juanma Barranquero
2011-12-29 16:57   ` Eli Zaretskii
2011-12-29 17:16     ` Daniel Colascione
2011-12-31 10:56       ` Eli Zaretskii
2011-12-31 11:04         ` Daniel Colascione
2011-12-31 11:22           ` Eli Zaretskii
2011-12-31 11:41             ` Daniel Colascione
2011-12-31 11:48               ` Eli Zaretskii
2011-12-31 15:23               ` Óscar Fuentes

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=24726464e3220fa8654e52357dfd56ab2d5bdb43.1325166907.git.dancol@dancol.org \
    --to=dancol@dancol.org \
    --cc=10399@debbugs.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).