View Single Post
Old 05-04-2016, 12:28 PM   #40
Jim Chapman
Addict
Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.
 
Posts: 310
Karma: 2025434
Join Date: Oct 2009
Device: Lumia 950 Phone
Quote:
Originally Posted by JSWolf View Post
To answer the topic's question, because a good number of apps ignore perfectly valid coding in ePub.
Reality check: using <p>&nbsp;</p> to represent a section break is 'valid' in the limited sense that the XHTML standard says that it is acceptable XHTML. But because the XHTML standard is not explicit about how you should display non-rendering non-whitespace, it does not tell us what a reading system has to do with that valid coding. It would be acceptable to ignore it (on the grounds that it is a P element containing no renderable content). It would also be acceptable to add a line containing nothing (on the grounds that it is a P element containing non-whitespace characters).

Sorry about the pedantry - but you know what it's like when someone is wrong on the internet ;-)

I agree that, pragmatically, the smart thing for e-reading systems is to treat <p>&nbsp;</p> as a section break, at least as an optional behaviour. It's just that you're using the word 'valid' a bit too loosely.
Jim Chapman is offline   Reply With Quote