You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've hit issues with rendering SVGs as well, and I've just spent some time tinkering with this to try and see if I could narrow it down.
Specifically, the problem comes about for me when using nested SVGs, which I am then converting to PNG. Here's the full text of an example SVG (Formatted for ease of seeing how it's nested):
The way it renders on my development machine, and what I would expect from bref, is this (One big SVG container, with a bunch of smaller SVG circles in it, placed in a grid):
But instead, they all pile up in the corner like so (ignore the bg, it's irrelevant):
Unfortunately, it doesn't appear to be as simple as compiling with --with-rsvg=yes or similar - In either case, convert -list configure | grep svg indicates that it's already enabled, yet running convert -list format | grep SVG lists MSVG, SVG, and SVGZ:
As opposed to my primary development machine, which lists MSVG, RSVG, SVG, and SVGZ:
I've got no knowledge of how to find out which one it's using to do the actual SVG conversion to PNG that I'm trying to accomplish... But I suspect that to be relevant.
Additionally, it also seems like the container is running ImageMagick 6.9.10, despite the Dockerfile explicitly downloading/installing 7.0.10-43. I can't help but wonder if the difference in version might also have something to do with it.
In any case, I'm at my wits' end here, but would be happy to help anyone troubleshoot so I can get this renderer I'm building up and running on Lambda via Bref.
I'm not really sure who would be best to talk to ... Based on git blame alone, it seems maybe @Nyholm@peldax or @chekalsky would be the ones most likely to know where to start?
Activity
V13Axel commentedon Mar 31, 2022
I've hit issues with rendering SVGs as well, and I've just spent some time tinkering with this to try and see if I could narrow it down.
Specifically, the problem comes about for me when using nested SVGs, which I am then converting to PNG. Here's the full text of an example SVG (Formatted for ease of seeing how it's nested):
You can easily test what I'm hitting with the following:
The way it renders on my development machine, and what I would expect from bref, is this (One big SVG container, with a bunch of smaller SVG circles in it, placed in a grid):

But instead, they all pile up in the corner like so (ignore the bg, it's irrelevant):

Unfortunately, it doesn't appear to be as simple as compiling with --with-rsvg=yes or similar - In either case,

convert -list configure | grep svgindicates that it's already enabled, yet runningconvert -list format | grep SVGlists MSVG, SVG, and SVGZ:As opposed to my primary development machine, which lists MSVG, RSVG, SVG, and SVGZ:

I've got no knowledge of how to find out which one it's using to do the actual SVG conversion to PNG that I'm trying to accomplish... But I suspect that to be relevant.
Additionally, it also seems like the container is running ImageMagick 6.9.10, despite the Dockerfile explicitly downloading/installing
7.0.10-43. I can't help but wonder if the difference in version might also have something to do with it.In any case, I'm at my wits' end here, but would be happy to help anyone troubleshoot so I can get this renderer I'm building up and running on Lambda via Bref.
I'm not really sure who would be best to talk to ... Based on
git blamealone, it seems maybe @Nyholm @peldax or @chekalsky would be the ones most likely to know where to start?