https://bugzilla.wikimedia.org/show_bug.cgi?id=3593
--- Comment #19 from Daniel Friesen <[EMAIL PROTECTED]> 2008-12-08 19:11:37 UTC --- (In reply to comment #18) > I think sending embedded SVG directly to clients is a *must*. There could be a > quick check for a compatible browser and if the user is using an old browser, > OK, fallback to a rasterised PNG. If you want this behavior could be enabled > in > the user preferences panel (I would personally enable it by default but...). > > BTW, wikipedia contains lots of SVGs, and when diagrams are uploaded as PNG > (or > worse JPEG) they insert a warning "This image should be recreated using vector > graphics as an SVG file" (see > http://en.wikipedia.org/wiki/Image:OO-historie.jpg). Why do they do that if > after all they're sending clients only pixels, pixels and more pixels? > > The reason for SVG is not only size (which may sometimes be big), it is its > vector nature (vs raster). You can print in high quality, you can zoom in the > page with Ctrl+Wheel and its always smooth. And also, client rendering can be > better than the generated PNGs: see > http://en.wikipedia.org/wiki/Singleton_pattern for example: the one generated > is wrong while FF and Chrome display fine. > Uhm, not to burst your bubble. But .svg images are not uploaded so that clients can zoom in the page. They are uploaded because thumbnails can be made in any size you want without loosing quality. That is independent of whether the browser or server does the rasterizing of the image. Now as for testing for browser support. There are multiple issues there: A) Testing for support is unreliable. We don't have a nice list of what supports what, and even if we did that changes, and support isn't always the best in older stuff. Obscure browsers which support it may end up off the list, while common browsers that don't support it as well may end up on that list. But because of the changing nature it's an unreliable feature, since it'll take part of a year between releases of MediaWiki for that list to change, and even then people don't always jump to updating right away. B) Support is also independent of the browser. You can get IE to work with SVG images if you install a plugin, but I don't believe that's something we can reliably test server side. C) Testing clients for .svg support and conditionally sending a .png or .svg will break the caching model. It won't be possible to properly cache a squid response with that kind of test, and will require extra server work that isn't necessary. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
