View Single Post
Old 09-13-2013, 05:01 PM   #31
William Ockham
Enthusiast
William Ockham can illuminate an eclipseWilliam Ockham can illuminate an eclipseWilliam Ockham can illuminate an eclipseWilliam Ockham can illuminate an eclipseWilliam Ockham can illuminate an eclipseWilliam Ockham can illuminate an eclipseWilliam Ockham can illuminate an eclipseWilliam Ockham can illuminate an eclipseWilliam Ockham can illuminate an eclipseWilliam Ockham can illuminate an eclipseWilliam Ockham can illuminate an eclipse
 
Posts: 36
Karma: 8164
Join Date: Jul 2012
Device: Kindle Keyboard
@Dylan Tomorrow: I didn't mean to suggest that these CSS3 features shouldn't be used in production ebooks. I do think that folks should be aware of the risks involved. To be (perhaps overly) pedantic, KF8 doesn't support any of these features. The webkit rendering engine used by the various devices supports these features. This matters to folks who produce commercial ebooks to be sold via Amazon. Just look at the current mess with the Kindle app on the iPad to see why.

My position is that the official format specs (EPUB 2 & 3 and KF8) are utterly useless because none of the leading devices and apps implement them in any sort of coherent fashion. Every so-called EPUB 2 device or app fails to properly implement CSS because they all break the cascade (for what are likely completely valid commercial reasons). Likewise, all of Amazon's KF8-compatible devices and apps have rendering engines that are far more capable that the spec would suggest.

You are much better off knowing how the Adobe and webkit engines render HTML and CSS than paying attention to the specs.
William Ockham is offline   Reply With Quote