View Single Post
Old 04-08-2010, 10:03 PM   #2
charleski
Wizard
charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.
 
Posts: 1,196
Karma: 1281258
Join Date: Sep 2009
Device: PRS-505
This boils down to a choice: CSS3 or XSL-FO.

Adobe has been in favour of XSL-FO for a long time. While it's more cumbersome to code than CSS, it's ultimately far more flexible and a far richer styling language. CSS3's paged media module is quite limited in comparison and has been stuck at working draft status for several years now, so it doesn't even have a finalised version to specify.

OTOH, while progress is somewhat glacial, web browsers are slowly moving towards support of CSS3 and web authoring will follow suit. From an implementation perspective, it's far preferable to allow those creating Reading Systems the ability to use the same renderer for both epub and web browsing functions on the same device.

Ultimately, I think CSS3 will win simply because it'll be easier to implement. Not a great reason, but possibly better than a situation in which Reading Systems implement an inconsistent subset of XSL-FO.
charleski is offline   Reply With Quote