From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, 10399@debbugs.gnu.org
Subject: bug#10399: [PATCH] Document win32 font backends
Date: Thu, 29 Dec 2011 09:16:16 -0800 [thread overview]
Message-ID: <4EFCA060.9000002@dancol.org> (raw)
In-Reply-To: <83pqf7uxhp.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On 12/29/11 8:57 AM, Eli Zaretskii wrote:
>> From: Juanma Barranquero <lekktu@gmail.com>
>> Date: Thu, 29 Dec 2011 17:21:08 +0100
>> Cc: 10399-done@debbugs.gnu.org
>>
>> On Thu, Dec 29, 2011 at 15:06, Daniel Colascione <dancol@dancol.org> wrote:
>>
>>> -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
>>
>> Committed, thanks.
>
> Please add there an @xref to "(emacs)Windows Fonts", where there are
> more details about that.
Doing that makes sense.
Since we're on the subject of Windows font backends: is it worth
creating a DirectWrite backend? It does a better job of inter-character
spacing and rendering at small sizes than Uniscribe does.
https://bugzilla.mozilla.org/show_bug.cgi?id=517642
https://blog.mozilla.com/nattokirai/2009/10/22/better-postscript-cff-font-rendering-with-directwrite/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
next prev parent reply other threads:[~2011-12-29 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 14:06 bug#10399: [PATCH] Document win32 font backends Daniel Colascione
2011-12-29 16:21 ` Juanma Barranquero
2011-12-29 16:57 ` Eli Zaretskii
2011-12-29 17:16 ` Daniel Colascione [this message]
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=4EFCA060.9000002@dancol.org \
--to=dancol@dancol.org \
--cc=10399@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lekktu@gmail.com \
/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).