MobileRead Forums - View Single Post - Bug

HarryT · 10-15-2009, 12:52 PM

Thanks to Paul for clearing this up.

The problem is caused by the fact the Book Designer (the tool I initially use to create my books) has a bug whereby when you add a table of contents entry, it puts a <span> tag in the wrong place, incorrectly nested with the surrounding tags.

Most devices seem to be pretty immune to this, but it seems that the PRS-600, for whatever reason, occasionally skips pages (presumably confused by the "never-ending span"). So, the error is in the file, but the PRS-600 is not as "fault tolerant" as perhaps it could be - this is not an error which affects the file "content" in any way, but it appears as though it can, from time to time, mess up the PRS-600's paging algorithm.

Unfortunately, this affects every ePub book that I've ever created, but luckily, with the overwhelming majority of them, it's harmless. For whatever reason, it really messed up this particular book on the PRS-600.

Obviously I'll make sure that I fix it on all my future books, and will correct it on the existing ones as and when I edit them. Luckily, as I say, even though the HTML is syntactically wrong, in the overwhelming majority of cases, it's completely harmless.

Thanks again to Paul for solving the perplexing problem!

10-15-2009, 12:52 PM	#22
HarryT eBook Enthusiast Posts: 85,557 Karma: 93980341 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	Thanks to Paul for clearing this up. The problem is caused by the fact the Book Designer (the tool I initially use to create my books) has a bug whereby when you add a table of contents entry, it puts a <span> tag in the wrong place, incorrectly nested with the surrounding tags. Most devices seem to be pretty immune to this, but it seems that the PRS-600, for whatever reason, occasionally skips pages (presumably confused by the "never-ending span"). So, the error is in the file, but the PRS-600 is not as "fault tolerant" as perhaps it could be - this is not an error which affects the file "content" in any way, but it appears as though it can, from time to time, mess up the PRS-600's paging algorithm. Unfortunately, this affects every ePub book that I've ever created, but luckily, with the overwhelming majority of them, it's harmless. For whatever reason, it really messed up this particular book on the PRS-600. Obviously I'll make sure that I fix it on all my future books, and will correct it on the existing ones as and when I edit them. Luckily, as I say, even though the HTML is syntactically wrong, in the overwhelming majority of cases, it's completely harmless. Thanks again to Paul for solving the perplexing problem!