View Single Post
Old 08-29-2014, 07:10 PM   #20
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
I use a fallback on the Kindle side (because older Kindle readers don't support SVG), but not on the EPUB side. SVG support is required for full EPUB spec compliance (even in EPUB 2), so as far as I'm concerned, if a reader doesn't handle SVG, the reader is hopelessly broken.

Experimentally, all mainstream EPUB readers handle SVG. I think I encountered a couple of old, semi-defunct readers that didn't handle SVG, but they mostly still rendered the text as block-level elements, which worked well enough for my purposes. Either way, they're lost in the noise.

Note, however, that there are a fair number bugs in various readers' SVG support. I've documented the various fix-ups that I perform on the SVG content over in the CSS and HTML tips section of the EPUB wiki page.
dgatwood is offline   Reply With Quote