Quote:
Originally Posted by JSWolf
Can you point me to which book and where the problem is? I can take the book to the Sony Style shop next week and have a go on the 900 to see if the problem exists since the 900 has a newer ADE.
|
sure, the book is volume 1 of the Thorndyke omnibus which i got
here. note that it doesn't happen consistently on *every* page, however it does happen a lot, so you might have to dig a little bit. according to mtravellerh, who posted it, it's a straight conversion to epub, presumably from mobi format (he doesn't specify). i took a quick glance at it just now and i see all paragraphs are enclosed in div tags rather than p tags, and that looks like bookdesigner code to me, so it wouldn't be suprising if something strange happened somewhere along the way since that's like the trifecta for bad code. but i really wouldn't expect the 900 to treat it any differently, nor should it.
Quote:
Originally Posted by Kolenka
If an ePub has improperly nested tags, that breaks the XHTML spec, and no proper XML reader is expected to read it. Now, more viewers are using an HTML renderer that's been pre-packaged, and will be much more lenient (accepting HTML4 rather than XHTML, which is against ePub spec, and so on)... but it doesn't mean those apps are right against ADE.
When ADE hits an improperly nested tag it ends that file right then and there, and will page break into the next XHTML file. This is true for the 900 as well.
|
yep. it's all about valid code.