View Single Post
Old 09-25-2014, 01:08 AM   #13
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
Quote:
Originally Posted by Jellby View Post
Not in ePub 2, with CSS3 (in ePub 3), it may be possible, see here. Whether any real reader will support it, I don't know.
To be pedantic, nothing prohibits an EPUB 2 reader from supporting CSS3 features, and nothing prohibits an EPUB 2 book from using them, so long as you're aware that those properties will be ignored by a sizable percentage of readers.

The key, IMO, whether you're designing for EPUB 2 or EPUB 3, is to design content in a way that degrades gracefully. If the specification you're designing for doesn't mandate support for a CSS feature that you want to use, you must make certain that your book still looks acceptable in readers that don't support that feature.

As for real readers, iBooks apparently supports it, and most WebKit-based readers on iOS probably do as well, at least in versions of iOS where CSS shape support is enabled by default. And in the MOBI world, KF8-based Kindle readers probably will in the future, whenever they move to a later version of WebKit.
dgatwood is offline   Reply With Quote