Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 03-19-2021, 11:17 PM   #2486
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 Dfaure View Post
I was suspecting KTE, because when I opened the epub in Calibre editor to remove "manually" the offending <span class="koboSpan">...</span> and related style definitions and finally transferred back the result onto the reader, I got back to the usual book reading behaviors.
The problem is that the spans are incomplete. They should have an id. What you have is:

Code:
<span class="koboSpan">
But, it should look like:

Code:
<span class="koboSpan" id="kobo.1.1">
The ids are used when storing the location. For the reading location, it is just the id. For annotations, it also has the a character count within the span.

I'd love to know where these came from. The spans without the ids are useless.

I'm not sure if adding support for this in the driver is worth it. It is a very unusual case. Or at least I hope it is. The check for the spans is simplistic and just checks that spans with this class or ids like the above exist. It doesn't check that they are valid. Adding something that fixes this would be beyond what I think is intended in the plugin. And I'm not sure how hard it would be or what risk of producing a bad result would be.

You can fix this with the editor. You can use Diap's Editing Toolbag plugin to remove them easily. The Modify ePub plugin can also remove spans. I can't remember if it has code to handle the kepubs spans or not. I know it was discussed, but, I don't remember whether it was added or not.
davidfor is offline   Reply With Quote