all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: lekktu@gmail.com, 10399@debbugs.gnu.org
Subject: bug#10399: [PATCH] Document win32 font backends
Date: Sat, 31 Dec 2011 12:56:54 +0200	[thread overview]
Message-ID: <83vcoxrouh.fsf@gnu.org> (raw)
In-Reply-To: <4EFCA060.9000002@dancol.org>

> Date: Thu, 29 Dec 2011 09:16:16 -0800
> From: Daniel Colascione <dancol@dancol.org>
> CC: Juanma Barranquero <lekktu@gmail.com>, 10399@debbugs.gnu.org
> 
> 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/

Looks like it has only C++ bindings?  One of the comments on MSDN
says:

  DirectDraw header file is not compatible with C programming language
  and can only be included in C++ code. However, C-style redeclaration
  of contents in this header file alone (excluding other header files it
  includes), will succeed in resolving the issue.

Also, I see no dwrite.h header in the MinGW runtime and w32api
distributions, and no lib*.a import libraries for dwrite.dll.  Am I
missing something?





  reply	other threads:[~2011-12-31 10:56 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
2011-12-31 10:56       ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83vcoxrouh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=10399@debbugs.gnu.org \
    --cc=dancol@dancol.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.