Re: [ft-devel] current cvs on suse 10

[Hans-Peter Jansen]

Am Montag, 21. November 2005 10:10 schrieb Werner LEMBERG:
> > While setting up 10.0 for an office environment, I noticed quite
> > bad font display due to kerning errors compared to earlier
> > versions.
> >
> > [...]
> >
> > That revealed a few problems, though. SUSE uses a patch to export a
> > bunch of methods from the ftstream module,
>
> Uh, oh, we are in the process of exactly the opposite, namely to
> limit the exported functions to the ones in the API.
>
> > Further investigation showed, that you're in transition from
> > FT_EXPORT to FT_BASE macros, but didn't finished yet
> > (FT_Stream_OpenGzip and FT_Stream_OpenLZW still used FT_EXPORT).
>
> Those two functions are tagged correctly since they are part of the
> public API.
>
> > I fixed it in a rather crude way in my rpm spec:
> >
> > find . -name \*.c -o -name \*.h | \
> >   xargs sed -i 's/FT_EXPORT(/FT_BASE(/g'
> > find . -name \*.c -o -name \*.h | \
> >   xargs sed -i 's/FT_EXPORT_DEF(/FT_BASE_DEF(/g'
> >
> > but still no bonus.
>
> You are completely misunderstanding what we are doing currently.  The
> proposed fix to apinames doesn't make sense.

Okay, thanks for the clarification and I do understand your intention.
That will help me to improve the hacks for now for a short time 
solution.

> > That leaves me with a couple of questions:
> >  - Should I prepare some (more) diffs from these issues?
>
> You should investigate why SuSE 10.0 uses internal symbols of the
> FreeType library.  This *must* be fixed.

You are right, but I'm not in the position to fix this for sUse now.
I'm willing to test the current fontconfig to see how it goes without 
those ugly hacks..

> >  - Any rough estimation on code maturity of current CVS?
>
> The code itself is as stable as before, basically.  We are going to
> simplify the compilation process, and the internal header files won't
> be installed any more.

Fine. I'm already hooked by the appearance of my desktop. 

If only OpenOffice UI would get this right, too:
https://bugzilla.novell.com/show_bug.cgi?id=134596

Pete