SVG in Wikipedia - SVG Open

More documents

Recommendations

Info

Cleanup squad! 200×236 PNG: 24.5k source SVG: 506k gzip SVG: 239k scoured: 237k gzip scoured: 49k 20x bigger! 10x bigger 10x bigger 2x bigger This map appears on the “San Francisco” article at a mere 200 pixels wide; the automatically rasterized PNG weighs in at about 24 kilobytes... but the raw SVG source is a whopping 20 times bigger! Even gzipped we’re 10x the size of the PNG; combining an automated run of Scour and gzip gets us down to 49k with no visible loss. We’re in the right ballpark but still more detailed than we need.
Simplify! Here we really need a more aggressive approach; we just have a lot of points that aren’t necessary for the image as we’re actually using it. Scour doesn’t yet support path simplification, but Inkscape does have a command for this. When heavily zoomed in we can definitely tell the difference...
Page 1 and 2: SVG in Wikipedia and Wikimedia Comm
Page 3 and 4: Wikipedia Our flagship site, and of
Page 5 and 6: Year 2009... 4 years of SVG MSIE 8
Page 7 and 8: Non-destructive editing http://comm
Page 9 and 10: Scaling Needs and technology evolve
Page 11 and 12: Scaling Needs and technology evolve
Page 13 and 14: Potential - linking (workaround OK)
Page 15 and 16: Potential - Interactivity (no worka
Page 17 and 18: librsvg bugs? Using a single render
Page 19 and 20: SVG challenges Size Security Speed
Page 21 and 22: Fat SVGs! Here I’m comparing the
Page 23 and 24: Category group Flags Icons Logos Ma
Page 25 and 26: Map madness! Wikimedians love to er
Page 27: Map madness! WTF? Wikimedians love
Page 31 and 32: Yay! ... but at intended screen siz
Page 33 and 34: Beware! Just applying simplificatio
Page 35 and 36: SVG challenges Security Size Speed
Page 37 and 38: Workflow To make participation easy
Page 39 and 40: Workflow? Ideally, we’d have a de

SVG in Wikipedia - SVG Open

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?