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
#6 tries to replace the batik svg to pdf converter with electron's printToPDF. At first glance, things are looking good on that front (ref #6 (comment)),
But, the old image server also uses batik to scale images (from a plotly svg to a scaled png). This gist compares the batik converter with two other node.js libraries (sharp and gm) and a browser-side solution.
The browser-side solution is looking good. It uses context.drawImage's width/height options for png/jpeg/webp formats and viewBox for SVGs.
Can anyone think of possible limitations for the browser-side solution?
The text was updated successfully, but these errors were encountered:
I can't think of any problems, and if anything I think browser-side should allow us to do better with the crispEdges issues #6 (comment) as it can apply crisp rendering after the image is already scaled up.
Uh oh!
There was an error while loading. Please reload this page.
#6 tries to replace the
batik
svg to pdf converter with electron'sprintToPDF
. At first glance, things are looking good on that front (ref #6 (comment)),But, the old image server also uses
batik
to scale images (from a plotly svg to a scaled png). This gist compares the batik converter with two other node.js libraries (sharp
andgm
) and a browser-side solution.The browser-side solution is looking good. It uses
context.drawImage
's width/height options for png/jpeg/webp formats andviewBox
for SVGs.Can anyone think of possible limitations for the browser-side solution?
The text was updated successfully, but these errors were encountered: