Re: [ft-devel] An analysis of Librsvg

[Vincent Torri]

On Wed, May 22, 2019 at 3:55 AM suzuki toshiya
<address@hidden> wrote:
>
> Dear Vincent,
>
> > Enligthenment, and more precisely the EFL (the libraries)
>
> Thanks. Please let me confirm a few points.
>
> * the supported elements
> In my understanding, the parser of SVG document is implemented
> in src/modules/evas/vg_loaders/svg/evas_vg_load_svg.c
> (
> https://github.com/Enlightenment/efl/blob/master/src/modules/evas/vg_loaders/svg/evas_vg_load_svg.c
> ),
>
> I think the elements supported by this loader are defined by
> TAG_DEF macro, thus, <use>, <circle>, <ellipse>, <path>, <polygon>,
> <rect>, <polyline>, <line>, and, <defs>, <g>, <svg>, <switch>
> are supported. Am I understanding correctly?

yes

> * input: xml support
> If I can spot the location of the SVG document parser, it seems
> that the parsing of SVG is helped by XML parsed in
> src/lib/eina/eina_simple_xml_parser.c
> (
> https://github.com/Enlightenment/efl/blob/master/src/lib/eina/eina_simple_xml_parser.c
> )

yes, it's a simple SAX-like parser



> * output: efl_gfx
> If I can spot the location of the SVG document parser, the
> rendering of parsed SVG is done by _efl_gfx_path_XXX() in
> src/lib/efl/interfaces/efl_gfx_path.c
> (
> https://github.com/Enlightenment/efl/blob/master/src/lib/efl/interfaces/efl_gfx_path.c
> )
>
> There is a comment "code adapted from enesim which was adapted
> from moonlight sources". Are they based on FreeType2?

here I have to ask. I'm not involved in the development of that part.
I'll ask the maintainers

Vincent