On Tue, May 14, 2019 at 8:37 AM Alexei Podtelezhnikov <apodt...@gmail.com> wrote:
> > > 3. *How much work to do make it work with FreeType*: Does it need a >> > C API wrapper? >> >> Yes. > > > Whatever external SVG renderer you choose, please use FT_Renderer facility > to hook it up with FreeType instead of creating a set of SVG specific > functions: an SVG glyph should be tagged as FT_GLYPH_FORMAT_SVG, which is > then picked up by the dedicated SVG FT_Renderer with hooks to external > library. The SVG support can be enabled/disabled using the renderer > modules, say "svg-ot", in modules.cfg. > EXACTLY. Also why I think, and said, that all the current energy is going in the wrong direction. Work can already be started implementing the SVG table and FT_GLYPH_FORMAT_SVG and then tested with any of the renderers before being any need to settle on one. Also, I have a version of NotoColorEmoji in SVG. I think at least checking how that renders with various renderers should also be part of the criteria for picking a default or recommending. > > https://www.freetype.org/freetype2/docs/reference/ft2-module_management.html > > > _______________________________________________ > Freetype-devel mailing list > Freetype-devel@nongnu.org > https://lists.nongnu.org/mailman/listinfo/freetype-devel > -- behdad http://behdad.org/
_______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
