Touch .kepub.epub

[tshering]

Originally Posted by clsdclsd

I just wanted to say that the highlight-not-working issue solved for me when I put the js in the book.

clsdclsd,
this is interesting stuff. Could you please provide me with a test file that demonstrates this?

[clsdclsd]

Originally Posted by jgoguen

I believe that would put the modified book into your library, not sure how else it could have happened. Maybe you added a book that had already been modified.

Somehow I've copied the books back with Calibre, but I cant remember when and how, and obviously it was unintentional. If I try to do it ("Add books to your Calibre library from the connected device") only one unrecognizable and unreadable file is transferred.
Anyway, a few hours of RegEx search&replace solved this :-). This was another lesson of the importance of backing up...

[clsdclsd]

friedmandu, tshering: I'm sorry, I just tried to put javascript to an another book, without success, so it seems that this method not works all the time. I can't share with you the book which was this worked on (or describe the procedure in details), but if you send me a file which has highlighting problems, I could try to cure that to see whether its working or not.

[tshering]

Originally Posted by clsdclsd

I can't share with you the book which was this worked on (or describe the procedure in details), but if you send me a file which has highlighting problems, I could try to cure that to see whether its working or not.

Actually, I do not have a kepub file with highlighting problems right now. Up to now I was able to find in each kepub that did not work as expected a way to make it work (most time I had to put each part that is referred to in the TOC into a separate file, or to change the file name, or put more kobo-tags into the files). Because of this and since I did not notice any improvement by adding the js file, I doubted whether the js file has any effect on reading the kepub on the Touch/Glo/Mini. Therefore I was curious to see your kepub and in which situations the js file improves its function.
Anyway, thank you for your offer to help.

[jgoguen]

What other Kobo tags did you have to add? Maybe it's something I can build in to the plugin?

[tshering]

Originally Posted by friedmandu

Could you help me a little with the procedure?
1) Do I merely take the kobo.js from another book and stick it into the book I'd like to enable for highlighting?
2) If I take the kobo.js from another book, there will be a lot of script already in the file (which to me is mostly gibberish). Is there any likelihood I can just apply that script to the target book as well?
3) And finally, how do I "reference it in the htmls"?
I hope this is not too difficult too explain. Thanks.

As a law-abiding citizen I would never dare to answer questions 1 and 2 with yes.
As for question 3, I take it to be a simple question on how to reference js files in general. You my google for it or have a look here

[tshering]

Originally Posted by jgoguen

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.

[Anak]

After using the KoboTouchExtended plugin to I found that
the first html-tag or span-tag after a <span class="koboSpan" id="kobo.1.1"> a white space before this tag is removed.

Original text (* represents a space, that is removed after conversion):

<h2>Moody’s plaatst vraagtekens bij waardering*<small>DE</small></h2>
…
<p>Het bod van*<span class="smallcaps">JAB</span> waardeert <span class="smallcaps">DEMB</span> in totaal op 7,5 miljard euro.

After Kobofying the epub:

<h2><span class="koboSpan" id="kobo.1.1">Moody’s plaatst vraagtekens bij waardering<small>DE</small></span></h2>
…
<p><span class="koboSpan" id="kobo.4.1">Het bod van<span class="smallcaps">JAB</span> waardeert <span class="smallcaps">DEMB</span> in totaal op 7,5 miljard euro.

Red: first html-tag/code: space removed
Green: second, third… html-tag/code: space not removed.

Is there a way to fix this? It should only be fixed if a white space precedes the first html-tag/code. Not just simply add one.

[Anak]

Originally Posted by jgoguen

As I've mentioned many times before, I can't include kobo.js or kobo.css, both of which are needed for many things (highlighting, annotations, bookmarks...) to work properly, because they are copyrighted non-distributable files.

I understand fully why you can include those files.
But nowadays the kobo.css is just an empty file and the kobo.js is the same in every kepub.
Kobo should not put these files into their kepubs but place them on their devices and write a routine that looks for them.
The only interesting thing i've found in the kobo.js is the "webkit-nbsp-mode" implementation by Kobo:

CSS property: -webkit-nbsp-mode
Description
Defines the behavior of nonbreaking spaces within text.
Syntax: -webkit-nbsp-mode: normal | space;
Values

• normal (default): Nonbreaking spaces are treated as usual.

• space: Nonbreaking spaces are treated like standard spaces.

Kobo.js
Kobo's implementation in the kobo.js file:

webkitNbspMode = 'space';

and could be changed to:

webkitNbspMode = 'normal';

Maybe this will work on sideloaded epubs if you add this to the reading section of the Kobo eReader.conf file:

[Reading]
readingWebkitNbspMode=normal

[buffaloseven]

The KED currently chokes when trying to send CBR/CBZ files to the Kobo Glo. Is there a chance you could add a small routine to check the type of file being sent and perform the extended features operations only on files that might support it, ignoring others?

[jgoguen]

Originally Posted by Anak

After using the KoboTouchExtended plugin to I found that
the first html-tag or span-tag after a <span class="koboSpan" id="kobo.1.1"> a white space before this tag is removed.

Original text (* represents a space, that is removed after conversion):

<h2>Moody’s plaatst vraagtekens bij waardering*<small>DE</small></h2>
…
<p>Het bod van*<span class="smallcaps">JAB</span> waardeert <span class="smallcaps">DEMB</span> in totaal op 7,5 miljard euro.

After Kobofying the epub:

<h2><span class="koboSpan" id="kobo.1.1">Moody’s plaatst vraagtekens bij waardering<small>DE</small></span></h2>
…
<p><span class="koboSpan" id="kobo.4.1">Het bod van<span class="smallcaps">JAB</span> waardeert <span class="smallcaps">DEMB</span> in totaal op 7,5 miljard euro.

Red: first html-tag/code: space removed
Green: second, third… html-tag/code: space not removed.

Is there a way to fix this? It should only be fixed if a white space precedes the first html-tag/code. Not just simply add one.

Originally Posted by buffaloseven

The KED currently chokes when trying to send CBR/CBZ files to the Kobo Glo. Is there a chance you could add a small routine to check the type of file being sent and perform the extended features operations only on files that might support it, ignoring others?

Please submit Guthub bug reports. Anak, you won't be able to attach the sample files there (I don't think so anyway) so I'll download them from here.

[buffaloseven]

Originally Posted by jgoguen

Please submit Guthub bug reports. Anak, you won't be able to attach the sample files there (I don't think so anyway) so I'll download them from here.

Rightio. Done.

[Anak]

Originally Posted by jgoguen

Please submit Guthub bug reports. Anak, you won't be able to attach the sample files there (I don't think so anyway) so I'll download them from here.

Done.

[paola]

Is the 2.5 upgrade going to affect Joel's plugin? I am thinking specifically of this post: if the kobo driver changes in Calibre, would Joel's plugin still work? I suspect this question may be technically daft, but by know you know I am no techie

[davidfor]

It will affect it in the same way that it affect the main plugin. Both have an option to support newer firmware, so just check that for the driver you are using. I have made the changes to the main plugin and they should be in the next calibre release. After that, there won't be a problem for either plugins. Unless one of us break some code.

Unfortunately, I have just remembered there might not be a calibre release this week. Kovid said he was going to be away and might not be able to do the release this week.