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
Thanks for your proposal, but I don’t think that we’re interested, for many different reasons.
First of all, we don’t use CairoSVG anymore, because WeasyPrint dropped Cairo a few years ago. We replaced it by an internal library inspired by CairoSVG, but that uses pydyf instead of Cairo for the output.
The current solution used in WeasyPrint is able to generate vector shapes directly in a PDF through pydyf. As far as I can tell (I can’t find the documentation), resvg generates raster images.
The current SVG implementation is limited (and some of its code is pretty awful), but it’s not ridiculous. If you miss some features or have blocking bugs, you can report them, and we’ll see if it’s possible to fix that.
We believe in web diversity, that’s why we’ve had the stupid idea to write our own HTML/CSS rendering engine 🙃. Let’s improve this implementation of SVG instead of killing it!
So… Long live resvg, and long live WeasyPrint’s implementation of SVG.
Hi,
it seems that resvg has better svg support than cariosvg.
Would you guys be willing to shift to
resvg
if i write a wrapper over it?The text was updated successfully, but these errors were encountered: