View Single Post
Old 11-16-2013, 04:53 PM   #841
arspr
Dead account. Bye
arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.
 
Posts: 587
Karma: 668244
Join Date: Mar 2011
Device: none
Exclamation Possible bug in KoboTouchExtended or in ACCESS renderer

Hi jgoguen

While reading a sideloaded kepubized epub, I've noticed a VERY strange behaviour with page numbers.

I've deleted the contents of the epub in order to make a simple test book and the trouble is still there. I upload that epub.

As you can easily check it has only 8 xhtml files. In order to make the bug evident, each file has a sample text with the following pattern: Name of the file -- Actual position / 8

What happens is that within ACCESS renderer, the page numbering of the book goes as follows:
  1. cubierta.xhtml No number (it seems that ACCESS doesn't show either header or footer in the very first file of the kepub. A logical decision as it is usually a cover).
  2. sinopsis.xhtml. Page 2 of 8.
  3. titulo.xhtml. Novel Title - Page 3 of 8.
  4. info.xhtml. Page 6 of 8. The bug starts here
  5. Prologo.xhtml. Page 7 of 8.
  6. dedicatoria. Page 8 of 8.
  7. Section0001.xhtml. Start - Page 4 of 8. Another jump in page numbers. In my original and true book this was the file with the main contents of the book. The behaviour was exactly the same as shown here, but this file has more than just one page.
  8. autor.xhtml. Author - Page 5 of 8.

I've re-re-checked the toc.ncx and the content.opf inside the epub and I don't see anything strange but I'm no expert. I've also checked that RMSDK doesn't show this behaviour when rendering the original epub.

As I don't know if the problem is within ACCESS or within your conversion from epub to kepub, I prefer posting here before going to the Kobo bug thread.

Could you check if there's something wrong with your plugin?

(As additional info I upload a screenshot of the plugin settings. I'm working with Calibre 1.11, FW 3.0.0 an KTE 2.2.13, I mean, newest versions in all the software).
Attached Thumbnails
Click image for larger version

Name:	KoboTouchExtended Settings.jpg
Views:	343
Size:	143.2 KB
ID:	115288  
Attached Files
File Type: epub Page numbers Test - Yo.epub (4.7 KB, 244 views)
arspr is offline   Reply With Quote