Using SVGs
See original GitHub issueWould it be possible to support SVG rendering?
![SVG doesn't work](image.svg)
or <svg><path...
Also it would be nice if there was an option to leave other file types alone and just let the browser render them as it would, without trying to parse them.
Thanks!
Issue Analytics
- State:
- Created 8 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Using SVG | CSS-Tricks
SVG is an image format for vector graphics. It literally means Scalable Vector Graphics. Basically, what you work with in Adobe Illustrator.
Read more >A Practical Guide to SVGs on the web
This guide aims to give a practical overview of how you can use SVGs on your websites — with some tips and tricks...
Read more >Use SVGs - Expo Documentation
SVGs (Scalable Vector Graphics) are a great way to present icons and other visual elements in a flexible, crisp, and performant way. Using...
Read more >SVG Tutorial - W3Schools
Advantages of using SVG over other image formats (like JPEG and GIF) are: SVG images can be created and ... SVG is an...
Read more >SVG files: what are they and how to use them? - Webflow
SVG stands for Scalable Vector Graphic and it's a 2D image or graphic file type. SVG files use mathematical equations and sets of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI, v4.2.0 contains a fix for this. Grip will now render SVGs when using Python 2.6 and below.
Thanks for opening and being patient with this issue, @akaleeroy!
I killed my Python 2 and installed Python 3.
mimetypes.guess_type
returns('image/svg+xml', None)
and grip works as expected.I do not know what the f^@# happened but f*^% Python on Windows. Thanks for the help, I guess you can close this now.