Quote:
Originally Posted by jackie_w
When you corrected the TOC ncx did you resend the new epub to just overwrite the old or did you fully delete the old (using the Kobo app's delete facility) before attempting the re-send? If the former perhaps the Kobo app is 'remembering' the old TOC ncx details rather than re-reading. It's just a thought - I have no factual observations to offer.
|
well I used " delete book" within the app, then download from dropbox to tablet, then import book. But who knows what fragments the database hangs on to.
Also, there's a lot of steps to check if I'm testing properly. like: 1. did I actually backup calibre to local dropbox folder. 2. did dropbox actually sync that to cloud, before I re-download to tablet... a lot of checking of file dates, to be sure that I'm testing the newly edited version & not just re-testing the old version. and I was being lazy & not also sending each edit to the aura HD to see how changes registered on that.
the main puzzle was not "can I fix it" , it was " why is it not already working".
my best theory ( given that I've now binned the dodgy source & moved on) is that I had that book for ages & I'd partially cleaned it myself in an old version of sigil, adding in some splits where 2 stories were in same "chapter". That was back in the day when sigil expected you to fix the toc by hand, mostly. so it was something to do with how I'd done the splits....
I did get a feeling, when I started to read it, that I'd read the opening short story once before, so probably I did a quick tidy of the book ages ago, ( added a couple of needed splits) , read a only bit of it , abandoned it, came back to it 2 - 3 years on when having a clearout....
Then for some reason I'd chosen this one & a few similar short story compilations as tablet testers so it has been travelling around via google play books, dropbox , on & off Kobo Arc, in & out of various Kindle Fire epub readers... & hence in & out of various android folders....
The book is scrapped now anyway, I just hoped someone would spot an obvious flaw in the posted code, that I was blind to.... or that someone would say, OH Yes, that happened to me once & it was because of .....
There's one simple instructive test for when I can be bothered. (maybe tomorrow)
Pick a well formed book.
change the nav value text for at least one chapter by directly editing the TOC in sigl or calibre editor,
(so that it differs from anything in the <head> section of the corresponding xhtml chapter file,)
then send that to aura via kepub converter and to tablet via calibre companion or dropbox,
then see what shows in footers on screen & what shows in the TOCs.
that should answer the thread title "where does renderer get footer info from "