freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ft-devel] 2.2 doc updates, tag moved


From: David Turner
Subject: Re: [ft-devel] 2.2 doc updates, tag moved
Date: Fri, 28 Apr 2006 11:07:52 +0200
User-agent: Thunderbird 1.5 (Windows/20051201)

Hi Steve,

Steve Langasek a écrit :
Hi David,

On Fri, Apr 21, 2006 at 10:50:07AM +0200, David Turner wrote:

I've just tested this version and found that there's a regression building
ft2demos 2.1.10 against it
First of all, the ft2demos release are *always* tied to the corresponding freetype2 one, which means that we do not guarantee that ft2demos 2.1.10 would build or work correctly with anything other than
FreeType 2.1.10

I guarantee you that this is not the first time that a new release of the font engine broke the build of a previous version of the demo programs. This is purely intentional, since we also use the demo programs to experiment
a bit (e.g. with the cache sub-system, or with the hint algorithms, etc...).

That's also why we always release both packages at the same time, with the same version numbers.
 because the prototype of FT_Stroker_New in
ftstroke.h has changed from
FT_EXPORT( FT_Error ) FT_Stroker_New( FT_Memory memory, FT_Stroker *astroker );

to

FT_EXPORT( FT_Error ) FT_Stroker_New( FT_Library library, FT_Stroker *astroker 
);

This seems to break binary compatibility with 2.1.7, which I understood was
a goal for the 2.2 release.

We changed the function signature because it was inconsistent with the rest of the API[1], and we know of no library or program that uses the stroker at the moment (except ft2demos), mainly because this component was still highly experimental and had some important bugs anyway. That is, until now (i.e. it is now stable and part of the public API)

We thus estimate that this will create zero problems. However, if you can name a single Debian package, except ft2demos that relies on the stroker, I'll accept to postpone the release a few days to revert the signature and provide an alternative
function that takes a FT_Library instead.

Regards,

- David Turner
- The FreeType Project  (www.freetype.org)

[1] Yes, I know the API isn't very consistent anyway, but let's not add oil to the fire...

Thanks,
------------------------------------------------------------------------

_______________________________________________
Freetype-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/freetype-devel


***********************************************************************************
Information contained in this email message is confidential and may be 
privileged, and is intended only for use of the individual or entity named 
above. If the reader of this message is not the intended recipient, or the 
employee or agent responsible to deliver it to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please immediately notify the address@hidden and destroy the original 
message.
***********************************************************************************




reply via email to

[Prev in Thread] Current Thread [Next in Thread]