> So, are there any plans for next major release in near future?
Yes, in autumn.
> Will the ABI change other than hiding these internal functions?
It will get a new major .so version (at least this was the concensus
on this list, IIRC), but there won't be any major changes in the code
itself, I think.
We probably should use libtool's `-export-symbols' option to really
hide the internal functions; any further advice on this topic is
highly welcome.
> Another issue specific to freetype is the licensing. I believe
> there are parts of library functionality covered by Apple license.
> Can you please shade some light on that?
A very small part of the TrueType hinting engine (exactly seven lines
of source code) is covered by two Apple patents -- not by a license,
BTW. By default, this code is disabled, and a work-around code can be
activated which handles most TrueType fonts just fine. Note that this
patent is basically valid in the US only since mathematical algorithms
can't be patented here in Europe.
> > We currently don't have a test suite, and we welcome volunteers.
>
> Yes, we can certainly identify some resources to look at this
> problem, thought we prefer to existing test suites if available. How
> does the testing happen today?
I run a test application over a bunch of strange and broken fonts and
check the results visually. Note that it is a very deep problem to
define an efficient test suite; ghostscript has exactly the same
problem, and, AFAIK, they don't have such a test suite either.
> Is it possible to develop test suites for this library using TET
> like framework?
What is TET?
> Any past freetype projects in test domain which we can leverage?
We have a bundle of demo applications (ft2demos) which test most of
FreeType's functionality.
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
