Inline SVG use
- Please review bias and prejudices about SVG in this article. It is urgent for Mediawiki the inline SVG, that can be parsed like any wikitext (!), or isolated in ordinary transclusion, to quarantine and collective-curator procedures.
Please, before deleting this message, add your comments to discuss here.
It's often suggested we use inline usage of SVG in place of rastered PNG:
Good:
- Use with templates: dynamically rendering figures with logical templates
- Scales better with client zoom
- Better print quality
- Potential for interactivity
- In some cases, faster transfer (SVG can have smaller file size)
Bad:
- More important to sanitize JS for browser security
- Possibly inconsistent rendering between clients
- In many cases, slower transfer (SVG can have much, MUCH larger file size than rendered PNG)
- In some cases, SVG originals are verrrrry slow display in browsers
- (try anything with filters! Example commons:File:Anime Girl.svg)
- No native Internet Explorer support before IE 9
Things to consider
[edit]Today, 2019... no problem (!! please implement full SVG suport on Wikipedia and intranet-Mediawikies!), only advantages!
- Is the most important issue for general data visualization (encyclopedic data and didactic view of data).
- Important issue for standard or templated Visual communication.
- Possible issue for interactive data visualization and templates, by D3js...
In 2017, no problem, only advantages!
Compatibility (as of March 2012)
- All major desktop/laptop browsers provide support for HTML5+SVG as well as for XHTML 1 + SVG
Compatibility for older browsers:
- http://code.google.com/p/svgweb/
- Flash+JS implementation of SVG rendering which provides support for IE. Could be interesting if reliable and performant!
Performance:
- A tool to decimate highly-detailed images to something that looks about the same in a more browser-sized way might be nice... still more scaling-friendly than a raster image, but could be much smaller than a super-detailed map of the entire US or something