> 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.
> 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.
> - What are your plans with this unofficial ftstream interface?
I don't know that. If it uses internal FreeType functions, it must be
rewritten to avoid that.
> - 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.
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
