unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Jason Rumney" <jasonrumney@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: bdf fonts in EmacsW32 ?
Date: Wed, 11 Jun 2008 13:54:38 +0200	[thread overview]
Message-ID: <f7ccd24b0806110454q60788c02kfe5bac90b86e2a16@mail.gmail.com> (raw)
In-Reply-To: <c0d75d06-dfe1-4c35-b899-e26ea420c424@x41g2000hsb.googlegroups.com>

On Wed, Jun 11, 2008 at 12:44, Jason Rumney <jasonrumney@gmail.com> wrote:

> But then I had second
> thoughts and will probably instead create a w32 freetype backend,
> which will provide support for many more font formats, but will
> require the freetype library to be installed.

That is nice to hear.

A few weeks ago I took a look at ftfont.c, with the idea of trying to
implement a freetype backend for w32 (I know very little about the
font handling in Emacs, but it would've been a great learning
experience). Unfortunately, I didn't go too far because, if I
understand it right, the new font code mixes three issues: font name
handling (I mean, XLFD vs. freetype names), glyph handling (uniscribe,
gdi, freetype) and font selection (fontconfig, native Windows API,
etc.). Excising fontconfig code from ftfont.c seems like a task for
someone who knows what he's doing :( :)

I think it'd be useful to have clear, different APIs for the three
aspects mentioned above. Or, if they exist, I missed them and would've
delighted to get a pointer...

   Juanma




  reply	other threads:[~2008-06-11 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11  9:07 bdf fonts in EmacsW32 ? Sergei
2008-06-11  9:45 ` Juanma Barranquero
     [not found] ` <mailman.13064.1213177535.18990.help-gnu-emacs@gnu.org>
2008-06-11 10:04   ` Sergei
2008-06-11 10:44   ` Jason Rumney
2008-06-11 11:54     ` Juanma Barranquero [this message]
2008-06-11 11:56       ` Juanma Barranquero

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=f7ccd24b0806110454q60788c02kfe5bac90b86e2a16@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jasonrumney@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.
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).