Hi, Sorry for spending your time by non-intuitive behaviour of validation modules and ftvalid.
On 14 Jun 2006 20:47:48 -0700 George Williams <[EMAIL PROTECTED]> wrote: >I tried ftvalid for the first time today. > >At first it just told me that every font I fed it was invalid. I >discovered this was because the default freetype does not include the >validation modules. After changing modules.cfg everything passed. Oops. Possibly the exist of ftvalid itself made you confused. At present, ft2demos builds ftvalid whenever the public APIs of validation modules (FT_OpenType_Validate()) are available, even if it's just pseudo function and the internal validation functions are disabled by modules.cfg. If it's bad idea, I will fix ft2demos/Makefile to build ftvalid only when the internal validation functions are enabled. Please let me know your thought. >I wonder... would it be possible to have FT_OpenType_Validate return >something other than FT_Err_Invalid_Argument if the validation service >is not present, and have ftvalid check for the <service missing> error >and generate an error saying that the service isn't present rather than >that the font is invalid? Sorry, when the internal validators are disabled, FT_XXX_Validate() should return FT_Err_Unimplemented, instead of FT_Err_Invalid_Argument. It was my mistake. I remember we had ever discussed this issue and agreed to implement so, when validation functions are decided to be disabled by default (around 2005-11?), but I slipped to fix that. Within 6 hours, I will fix it in CVS. Thanks and Regards, mpsuzuki _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel