Hi,

I wanted to give a brief update on the work done this week.
Most of it was discussed in the mailing list however, just for
completeness sake, I would briefly describe it in this email.

I wrote the rendering ports for `librsvg' as well as `svgnative'.
So, in total, we have three rendering ports: resvg
<https://bitbucket.org/moazin/resvg-port-freetype-otsvg/src/master/>,
librsvg
<https://bitbucket.org/moazin/librsvg-port-freetype-otsvg/src/master/>
and svgnative
<https://bitbucket.org/moazin/svgnative-port-freetype-otsvg/src/master/>.
Note that some of these may not work with
the tip of `GSoC-2019-moazin' branch, because I am trying
out different ideas and can't update every port to work with
the tip of `GSoC-2019-moazin'.

Meanwhile, Toshiya wrote a thin C-API for `svgnative' and
I updated my `svgnative' port to use that instead. Note that
`svgnative', at the moment, doesn't have a `render_by_id'
feature, so I am waiting for it to be implemented, once that's
done, I'll update the port to support SVG docs which contain
multiple glyphs. At the moment, both `resvg' and `librsvg'
ports have this support. :)

There were some clipping issues with the `resvg' port, which
were only because I was making a mistake with the function
call, I solved that
<https://bitbucket.org/moazin/resvg-port-freetype-otsvg/commits/e7f3c4e4844386e93c2113adab1d845e2ea97b22>.
A little part of the glyph was getting clipped,
this was because I wasn't performing any rounding in the
bounding box, but instead just chopping the fractional parts.
I fixed
<https://bitbucket.org/moazin/resvg-port-freetype-otsvg/commits/eb2dc081c3c1d5954564f36e6eac8d5d2a8ffe0a>
those.

Apart from these, I spent some time finding memory leaks
and ultimately solving them. This has been giving me some
trouble, but I think I am near the right solution now. All of the
leaks that I knew off are fixed now, I have checked using FT
Memory debugger as well as valgrind.

At the moment, I am trying out the idea given by Alexei
about removing the whole hooks mechanism and creating a
separate module for each SVG rendering library. Once, It
reaches a good state, we can have a look at both attempts
and discuss them. :)

Best,
Moazin
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel

Reply via email to