Re: PangoXft and PangoFT2 patch from hell

[Tor Lillqvist <tml iki fi>]

Alex Larsson writes:
 > > What do you suggest 'for now'. I guess porting mini-xft is at least
 > > some hours of work. A _really_ short look at the code gave me the
 > > impression, that it is tightly bound to the *ix way of doing things.

Well, just making it build (with gcc; MSVC will need some #ifdef
HAVE_UNISTD_H etc) was not that hard. Whether it actually does
anything sensible is another matter. Anybody have a simple (but not
too simple) working test program for pangoft2? (I don't think the old
viewer-ft2.c in Pango's examples compiles any longer?) What should an
XftConfig file look like? (Oh well, that can probably be found on the
web.)

 > > Otherwise what are the policies for porting mini-xft to win32 ?
 > > #ifdef _MSC_VER, HAVE_GLIB_H and G_OS_WIN32 .... ?

For now, I just used #ifdef _WIN32, as mini-xft doesn't use GLib.

 > > Or should pango-ft2 simply be disabled for now and worked around
 > > it on the application level (The Gimp currently depends on it.)

Ah, yes, HEAD GIMP, that is a test program, even if not that simple
though ;-) (I have stayed away from HEAD GIMP so far, left that to
Hans.)

--tml