Thread: Touch .kepub.epub
View Single Post
Old 04-15-2013, 04:22 AM   #202
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by jgoguen View Post
What other Kobo tags did you have to add? Maybe it's something I can build in to the plugin?
Sorry, I meant to say "further kobo id span tags (span id="kobo.1.1" and so on)." For instance, if a chapter is so long that it results in a certain screen page having no opening kobo span tag and you happen to close the book on this screen page, the book will not reopen at the correct screen page. As you might have noticed. in the preview kepubs from Kobo (and I therefore suppose also in the regular Kobo kepubs), they put a kobo span tag also in between sentences (with increasing second index number); in some books they additionally match each font attribute tag with a kobo span tag. Since the screen page breaks are depending on customizable values like font attributes, margins and so on, even those measures (namely, further kobo span tags) will not prevent kobo-span-tag-less screen pages in every possible case, or one will end finally putting kobo tags around each single letter.

The other problem I had was with ranges of text that were not at all covered by kobo span tags, as for instance tables and lists. This was of course my fault, since I did not think of those case at all to start with.

I do not know about your plug-in (and I do not know whether calibre changes tables and list to some other constructions), but judging from your description earlier in this thread your plug-in might be prone to these problems too.

Last edited by tshering; 04-15-2013 at 04:36 AM.
tshering is offline   Reply With Quote