>
> Why is it an issue even with clipping? [...]
Not a big issue. Such inaccuracies are rare, but when they do pop-up, the
inaccuracy isn't a problem. The same happens with Cbox calculation in
traditional glyphs and we are fine with it too. :) The glyph will still
land up at the right place.
>
> Technically it isn't rendering it to pixel data. A Cairo recording surface
> just records the drawing operations without rendering it to pixels (AFAIK).
> Then it uses those recorded operations to find bounds.
Why is it an issue even with clipping? The clipped bounding box can be
very well est
Technically it isn't rendering it to pixel data. A Cairo recording surface
just records the drawing operations without rendering it to pixels (AFAIK).
Then it uses those recorded operations to find bounds.
On Thu, Aug 8, 2019, 9:54 PM Alexei Podtelezhnikov
wrote:
> > This hook function (for libr
> This hook function (for librsvg) would work in the following manner:
> * create a cairo recording surface
> * render the glyph on that surface (you'll have to check whether to render
> the whole document or a particular element)
This is unacceptable because it defeats the purpose. If the librar
