Thanks for suggestions.I also want to see all possible libraries and opt only the best of them. I am totally open to either modular or API editing approaches. I have clone the repo from earlier and working on some quick tests. And thanks for clearing my doubt about otvalidator. -Alekh
On Tue, 5 Mar 2019, 11:03 am Werner LEMBERG, <w...@gnu.org> wrote: > > >> I had also discussed about *librsvg* by GNOME as potential library > >> that can fit the job. Although as told by Werner Sir it is porting > >> to rust but still its API is in C. > > > > `librsvg-2' looks fine to me: [...] > > I still want an evaluation of various SVG libraries as part of the > GSoC project describing pros and cons – even if used only to reject > everything but `librsvg-2'. > > >> Whether to edit both Glyph positioning (otvgpos.c) and substitution > >> tables (otvgsub.c) or only positioning,I want to know about this. > > > > I am not sure about that, Werner might have an answer for you > > there :) > > Please completely forget `otv*'; this is not related to SVG support. > The idea of SVG handling is very simple: > > * Extract the SVG data from the `SVG' table, > * build a proper SVG document and send it to the SVG library for > rendering, > * receive a bitmap (or pixmap) and use it similar to other bitmap > glyphs within FreeType. > > There is no higher-level stuff to consider. Just follow the OpenType > specification. :-) > > > Werner >
_______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
