Hi everyone,
I just removed FT_Get_Module_Flags, it is now replaced by a new API
named FT_Get_TrueType_Engine_Type. documentation is below.
I guess It will be part of the next release candidate
Regards,
- David Turner
- The FreeType Project (www.freetype.org)
-- cu
On Mon, 2006-02-20 at 13:24, Owen Taylor wrote:
> On Mon, 2006-02-20 at 21:39 +0100, Werner LEMBERG wrote:
> > > Could someone tell me the relevance of the new public API named
> > > FT_Get_Module_Flags that
> > > was introduced in the current CVS ?
> > This is OK with me. Owen?
>
> Wasn't me..
On Mon, 2006-02-20 at 01:56, david turner wrote:
> If this function's purpose is to determine wether the bytecode
> interpreter is activated in a given
> FreeType build, I'd rather like to see a specific API that returns a
> boolean, or an enum, instead
Can't you avoid even that by using dlopen(N
Hi,
On Tue, 21 Feb 2006 17:06:35 +
David Turner <[EMAIL PROTECTED]> wrote:
>CVSROOT: /cvsroot/freetype
>Module name: freetype2
>Branch:
>Changes by:David Turner <[EMAIL PROTECTED]>06/02/21 17:06:35
>
>Modified files:
> . : ChangeLog
> src/s
> This small program can dump the outlines, hinted or unhinted, of
> glyphs under windows. It is helpful for identifying whether certain
> rendering differences result from the bytecode interpreter or from
> the monochrone raster.
Very good that you've written that! I've asked for such a progra
On Wed, Feb 22, 2006 at 08:46:12AM +0100, Werner LEMBERG wrote:
> Very good that you've written that! I've asked for such a program
> years ago. BTW, perhaps you find a better name for this smal
> program...
On my box, I name it `a.c' :-)
> Using FontForge to single-step through the bytecode ins
