>> I still favour the model of having a *single* default renderer for >> SVG, providing hooks that can be overridden at run-time for another >> library. > > This is not user friendly and users will resist it.
If I'm going to use a non-default SVG engine then I clearly expect some lines of code for doing this. Why do you consider this not user-friendly? > 4) FT_Set_SvgHooks (at least use FT_Property_Set instead) Using `FT_Property_Set' instead of `FT_Set_SvgHooks' is a good suggestion, thanks! Moazin, what do you think? We would have one API function less. https://www.freetype.org/freetype2/docs/reference/ft2-properties.html Werner _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
