View Single Post
Old 12-14-2009, 11:09 PM   #18
Peter Sorotokin
speaking for myself
Peter Sorotokin knows what time it isPeter Sorotokin knows what time it isPeter Sorotokin knows what time it isPeter Sorotokin knows what time it isPeter Sorotokin knows what time it isPeter Sorotokin knows what time it isPeter Sorotokin knows what time it isPeter Sorotokin knows what time it isPeter Sorotokin knows what time it isPeter Sorotokin knows what time it isPeter Sorotokin knows what time it is
 
Posts: 139
Karma: 2166
Join Date: Feb 2008
Location: San Francisco Bay Area
Device: PRS-505
Quote:
Originally Posted by Valloric View Post
I saw it the first time, and couldn't believe you said it. Then I saw it the second time, and I still can't believe you said it.

Rendering HTML + CSS correctly is horribly difficult. Throw in SVG which the EPUB standard supports and now it's eyeball-gouging difficult. I mean geez, half the Webkit source tree is SVG, and the other half still makes for hundreds of thousands of lines of code. And Webkit is considered light.

So no, rendering EPUB files is not easy. It's far, far from easy. It's the reason why Adobe chose Webkit as the basis for their ADE renderer.
Adobe EPUB renderer currently does not use Webkit. But you are right that doing XHTML+CSS correctly is very difficult. This is the main reason why we still don't do everything correctly. (SVG is actually a bit easier once you have decent drawing library).

Still, doing EPUB renderer is significantly easier than doing a browser. One reason is that you don't need to implement interactivity and JavaScript integration. The other is that you don't need to match legacy HTML rendering.
Peter Sorotokin is offline   Reply With Quote