Dear Behdad, Alexei wrote: > 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.
Behdad wrote: > EXACTLY. Also why I think, and said, that all the current energy is going in > the wrong direction. Could you tell me more about "all the current energye is going in the wrong direction"? Do you think "spending much energy for the discussion which is not so much important"? Or, do you think "trying to implement something in wrong design"? > 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. Ah, maybe the implementation of the SVG table parser might be the most stable part, regardless with which SVG renderer is good, how it is collaborate with FreeType. It's correct. Regards, mpsuzuki _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
