-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Selection of Renderer #379
Comments
Just a librsvg wrapper. They can do some basic rendering manually, but it doesn't worth considering.
This is Chrome. Same as resvg-test-suite/tree/master/tools/chrome-svgrender, but more user-friendly.
WebKit wrapper. The same as Chrome.
The libs and apps I've chose test rendering backends. There is no point in testing wrappers. The list you provide on wiki is a bit pointless, because there are like 5 decent SVG implementations (Chrome/WebKit, Firefox/Gecko, resvg, batik, rsvg and Inkscape). Everything else is either useless or just a wrapper.
This is just QtSvg
Extremely primitive.
Extremely primitive.
Proprietary.
Dead? Proprietary?
Dead. Proprietary.
Dead?
Proprietary.
Dead
Dead |
Thanks for clarifying, that's exactly the information I was looking for. (Sorry for bugging you, I was unable to find/understand the backend-information.) |
No problem. |
I tried to collected several svg2png-render on SVG-renderer
ImageMagick, svgexport, PhatomJs are imho often used, but SVG.NET, QtSvg, wxSvg are hardly listed
Is there a reason why you choose those you listed in #svg-support, e.g. do they use a backed which is already tested?
The text was updated successfully, but these errors were encountered: