View Single Post
Old 02-23-2019, 06:22 AM   #13
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 rashkae View Post
Per the first post, the problem with not remembering the reading position only happens *after* he added the covers. That leaves us trying to guess what exactly it is about the final file that is causing the issue, or trying to replicate it by assuming what he's doing.
I think it's a combination of the internal file names, adding the cover and sending as a kepub. I think the NCX file gets rewritten along the way and the "bad" characters are escaped. With the way Kobo stores and uses the ToC in the database, and the reading position, I think there is a conflict between where characters have been escaped and where they haven't been.

But, I'm having problems reproducing it. I had if failed as described once, fiddled and fixed. But, I cannot revert and have it break. But, I am sure that cleaning/simplifying the internal file names will fix it.
davidfor is offline   Reply With Quote