> I'm sorry but I don't understand. My understand is:
>
> The area specified by 0xFF is reserved for passing a new series
> of information which controls a different function of a validator
> to the validator.
>
> My understand is correct?
Almost:
Bits 0 to 7 are used for the gl
> > Why FT_VALIDATE_BASE is started from 0x0100?
> > It seems that 0xFF is reserved.
>
> It was just convenience -- a new series of information which has a
> different function.
I'm sorry but I don't understand. My understand is:
The area specified by 0xFF is reserved for passing a new serie
> Why FT_VALIDATE_BASE is started from 0x0100?
> It seems that 0xFF is reserved.
It was just convenience -- a new series of information which has a
different function.
> I guessed this 0xFF is reserved for passing the validation level.
> Using this reserved area, it is easy to pass a validation
> > I have found that there is no way to pass FT_VALIDATE_DEFAULT,
> > FT_VALIDATE_TIGHT not FT_VALIDATE_PARANOID to FT_OpenType_Validate.
> >
> > Always FT_VALIDATE_DEFAULT is used. Is it expected behavior?
>
> Yes, more or less. I've modeled the validation code after the cmap
> validation cod
> The function declaration for FT_Outline_Embolden in ftoutln.h is
> using the wrong export macro.
Fixed in the CVS, thanks.
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
