Re: PangoXft and PangoFT2 patch from hell

[Hans Breuer <hans breuer org>]

At 11:22 17.11.01 -0500, Owen Taylor wrote:
>Sven Neumann <sven gimp org> writes:
>> Alex Larsson <alexl redhat com> writes:
>> 
>> > [...]
>> > The minixft.tar.gz tarball must be unpacked in $SRC/pango/mini-xft, and 
>> > contains a copy of Xft without X dependencies.
>> 
But it doesn't build out of the box (after an hour of work) on win32/msvc.

>> I don't see the benefits of this approach and don't like the idea of 
>> wrapping Pango closely around Xft.
>> [...]
Me neither but I guess it's too late now :)

> [...]
>
>On systems using Linux, MiniXft is clearly the right way to go.
>On Win32 systems, we might want to eventually investigate some
>sort of mechanism where the FT2 library could share the same
>font lookup system as the Win32 backend. That's too ambitious
>for now.
>
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.

If there is a vision for doing it right the first time for win32
I would like to here about it.

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

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

My suggestion to partly resolve this issue 
http://mail.gnome.org/archives/gtk-devel-list/2001-August/msg00612.html
was dropped as 'pango_give_me_a_random_unknown_context_so_my_app_can_break'
and 
'I fail to see the problem. The FT2 backend should build and run on win32.'

So I shouldn't have brought this up again :)

Thanks,
	Hans

-------- Hans "at" Breuer "dot" Org -----------
Tell me what you need, and I'll tell you how to 
get along without it.                -- Dilbert