Bug - with book or with Sony ePub renderer? - Page 2

JSWolf · 10-14-2009, 10:31 PM

Quote:

Originally Posted by HarryT

I've decided to recreate this book, from the original sources, one item at a time and see if I can pin-point exactly where it goes wrong. This is really bugging me now!

Did you try the copy I put up?

HarryT · 10-15-2009, 02:49 AM

Sorry, Jon; I should have thanked you for that. Yes, your version works fine! But I want to find out just what it is about my version that the PRS-600 doesn't like.

HarryT · 10-15-2009, 06:14 AM

I've now managed to reduce this to a "minimalist" case. One story, in a 13k HTML file which, when converted to ePub, fails.

Again for the PRS-600 select the "M" font size, and page through the book. It goes from "or pleasant in their..." at the bottom of one page, to "... difficulty of reduction" at the top of the next, missing out the page in between.

If anyone can see ANYTHING in this HTML or ePub file which might be an issue, I'd be VERY grateful to know what it is!

pdurrant · 10-15-2009, 09:21 AM

I think your problem is down to the entire content being enclosed in a span. Removing this, without any other cleanup (which is needed) fixes the problem on my system. I enclose bug and bug2, which show the difference, and are even more minimal than yours.

I'd suggest working towards getting it to pass epubcheck at least.

Quote:

Originally Posted by HarryT

I've now managed to reduce this to a "minimalist" case. One story, in a 13k HTML file which, when converted to ePub, fails.

Again for the PRS-600 select the "M" font size, and page through the book. It goes from "or pleasant in their..." at the bottom of one page, to "... difficulty of reduction" at the top of the next, missing out the page in between.

If anyone can see ANYTHING in this HTML or ePub file which might be an issue, I'd be VERY grateful to know what it is!

HarryT · 10-15-2009, 09:50 AM

Brilliant - thanks, Paul; that does indeed fix the problem.

Many thanks!

comtrjl · 10-15-2009, 12:44 PM

Well done, pdurrant. Must be the Norfolk air.
I've spent ages futzing around with this with little new to report.
But paging through the cut-down version (in the Sony software) which Harry posted today I had a missing page, as expected. I unzipped it, edited the 3rd html file to remove the 2 square brackets and the 2 following lines and when I paged through again, there was the missing page in all its glory. Then work intervened and I had to stop, but strange to say, everything did seem OK.
Glad it's fixed.

bob

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!

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
iBooks - ePub - Linking Bug	lcoleman79	Apple Devices	2	06-30-2010 11:06 AM
0.6.37 convert to ePub bug(?)	cutterjohn42	Calibre	1	02-05-2010 09:14 AM
Classic Nook as an ePub renderer: review	kjk	Barnes & Noble NOOK	1	12-11-2009 01:36 PM
Bug in Adobe EPUB implementation	Lord KiRon	ePub	3	09-05-2009 09:06 AM
In-Device PDF Renderer Modification	Conrad	Sony Reader Dev Corner	3	05-12-2009 05:21 AM

10-15-2009, 02:49 AM	#17
HarryT eBook Enthusiast Posts: 85,544 Karma: 93383043 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	Sorry, Jon; I should have thanked you for that. Yes, your version works fine! But I want to find out just what it is about my version that the PRS-600 doesn't like.

10-15-2009, 09:50 AM	#20
HarryT eBook Enthusiast Posts: 85,544 Karma: 93383043 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	Brilliant - thanks, Paul; that does indeed fix the problem. Many thanks!

10-15-2009, 12:44 PM	#21
comtrjl Connoisseur Posts: 75 Karma: 204999 Join Date: Aug 2006 Location: London	Well done, pdurrant. Must be the Norfolk air. I've spent ages futzing around with this with little new to report. But paging through the cut-down version (in the Sony software) which Harry posted today I had a missing page, as expected. I unzipped it, edited the 3rd html file to remove the 2 square brackets and the 2 following lines and when I paged through again, there was the missing page in all its glory. Then work intervened and I had to stop, but strange to say, everything did seem OK. Glad it's fixed. bob

10-15-2009, 12:52 PM	#22
HarryT eBook Enthusiast Posts: 85,544 Karma: 93383043 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!

Advert

Advert