> For 2, yes, there is the burden of writing the hooks and it is an intensive > task. But that's the cost of plugging in other libraries. For popular > libraries > like `resvg', `librsvg' and `svgnative' I am going to write the hooks myself > (I already have, just need to update them), and the users can use those. > There are no header inclusions in this case from FreeType side, but yes, > the client application will have to include the respective headers of the > SVG rendering library and also link against it.
Yes, yes. This needs documentation with hook prototypes described and the presets demonstrated with examples. > If users wants to plug some brand new library, > they'll need to write a new module. IMHO, that's equally intensive. Equally? C'mon! The new interface is supposed to be better then modules, I thought. _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
