vpelletier
commented
11 years ago Fiddling more, I realised it was not possible to annotate/highlight text, so I searched for the solution... Which turns out to also fix the problem I reported here. I do not exactly know what fixed the issue, but I:
- added
<span id="kobo.X.Y">...</span>in many places - added a kobo.js (and imported it in all pages)
Spans alone didn't do the trick, so I guess the reader program is calling some of the js functions.
To summarise my understanding:
*.epubfiles use a renderer which doesn't have all the bells and wistles I wished for (smallcaps, text-trasform, ...) but is integrated with kobo features without needing to alter the book specificaly for them*.kepub.epubuse another rendered which has them, but has stronger requirements than the epub standard in order to integrate with kobo stateful features (save position with page-level granularity, annotations, bookmarks, highlights, and possibly font tweaks although I couldn't enable them yet).
As I originally thought *.kepub.epub was just a way to select an epub3-enabled renderer and that any epub3 would just work out of the box with all features the epub2 renderer has, I close this ticket wontfix-ish.
Giving a try at composing an a public domain text into an epub (2, then 3), I could trigger the issue where a book does not open at the page it was last left on my kobo glo. I didn't get the issue on an epub2 (.epub) but triggered it on an epub3 (.kepub.epub) by having a single xhtml file for a whole chapter. Exiting the book in the middle of a multi-page chapter and re-opening it brings to chapter beginning. Bookmarking (tap-at-page-corner) behaves similarly, the folded-corner image appears at chapter beginning when reopening the book. Suspending and resuming while the book is opened doesn't trigger the issue. If you wish, I can send you the ebook file for testing.