Thread: Aura HD whre does kebub renderer look for footer chapter title
View Single Post
Old 04-29-2014, 08:38 PM   #9
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by cybmole View Post
a new test

so to puzzle out more of my own ocnfusion I took a different book & delibarately picked an awkward one whth had 2 <h2> tage per chapter.

then I added the word test into the toc file
so I had this code:
Code:
<navPoint id="navPoint-2" playOrder="2">
      <navLabel>
        <text>1</text>
      </navLabel>
      <content src="Text/chapter01.xhtml"/>
    </navPoint>
    <navPoint id="navPoint-3" playOrder="3">
      <navLabel>
        <text>THE BEGINNINGS OF CHRISTIAN SCRIPTURE test</text>
      </navLabel>
      <content src="Text/chapter01.xhtml#sigil_toc_id_1"/>
    </navPoint>
I sent that via the kepub plug in to aura HD.

What I see in the footer for that chapter is the number 1 - so it seems to take the 1st toc entry that links to that xhtml files and use that as it's foot label.
There was some discussion on this here last year. From memory you are right. The chapter at the bottom is the first TOC entry in the file. But, I don't remember if the page count was done for the file or for the chapters in it.
Quote:
that book also had a chapter called conclusion. Only one toc entry for that chapter, so I changed it to to say conclusion test, and that is what shows in the footer on the aura. so the renderer uses what is in the toc, not what is in the chapater html file.
Yes, the Kobo e-ink devices use the NCX for their navigation. But, they read it when the book is first put onto the device and load it into the internal database. The navigation actually uses the database entries rather than reading the NCX when you are reading the book.
Quote:
in hte aura toc I ahve both of the entires shown above & both go to the same place.
That should only happen if they are on the same screen. I have quite a few books with a main chapter heading for the file and sub-chapters within. The navigation works as expected. But, it will go to the start of the file if the anchor doesn't exist in the file.

I can't comment on the android and google play behaviour as I don't use either. Well, other than saying it sounds like Google got it wrong.
davidfor is offline   Reply With Quote