Touch .kepub.epub - Page 11

tshering · 03-11-2013, 10:04 AM

Yesterday I got an epub and converted it to a kepub.epub. The device did not remember the last opened page and opened the book always with the first page. When I navigated via the TOC menu, annotations and highligths did not show and it was not possible to insert new ones.
This was caused by the url-encoding of the filenames in the toc.ntx. The filenames followed the pattern "CR!Ssomething_split_000.html", whearas the references in the toc.ntx followed the pattern CR%21S_split_000.html". After changing "%21" to "!" everything went fine.

jgoguen · 03-11-2013, 11:32 AM

Quote:

Originally Posted by tshering

Yesterday I got an epub and converted it to a kepub.epub. The device did not remember the last opened page and opened the book always with the first page. When I navigated via the TOC menu, annotations and highligths did not show and it was not possible to insert new ones.
This was caused by the url-encoding of the filenames in the toc.ntx. The filenames followed the pattern "CR!Ssomething_split_000.html", whearas the references in the toc.ntx followed the pattern CR%21S_split_000.html". After changing "%21" to "!" everything went fine.

Can you please submit a Github bug report for this?

jgoguen · 03-11-2013, 11:37 AM

Quote:

Originally Posted by eXistenZ

Maybe I'm wrong but a workaround could be to add tho the plug-in an option so any user can select the Js file from his computer, so you don't need to redistribute it, but everyone can legally (I think) take a free kepub from kobo, extract the JS file and point the plug-in to it.

It should work if the file is the same in every kepub.

The only concern is whether this counts as "aiding distribution of copyrighted content" and if that is legal. If this were a generic ePub plugin that just so happened to do Kobo-ification and also just so happened to allow adding arbitrary scripts, that would clearly be allowed, but this plugin would have no purpose for that other than loading Kobo-specific scripts. I've not been able (yet) to get a clear answer on that. If it turns out that it isn't, I'd be happy to add such an option. I can read the Canadian law again, but I would appreciate it if anyone more familiar with American law could comment on this from an American perspective. The legalities of other countries would be appreciated too, but Canadian and American are the ones that affect me directly.

tshering · 03-11-2013, 12:01 PM

Quote:

Originally Posted by jgoguen

Can you please submit a Github bug report for this?

It is not a bug of the plug-in! I should have clarified that I did not use your plug-in. I just wanted to share that the kepub rendering engine does not like this kind of url-encoding. I did not test it, but this encoding might probably create the same problems with a normal epub.

jgoguen · 03-11-2013, 12:31 PM

Oh, sorry about that

Looks like something I should make sure the plugin handles... since I'm in there editing stuff anyway.

tshering · 03-11-2013, 12:39 PM

Quote:

Originally Posted by eXistenZ

Maybe I'm wrong but a workaround could be to add tho the plug-in an option so any user can select the Js file from his computer, so you don't need to redistribute it, but everyone can legally (I think) take a free kepub from kobo, extract the JS file and point the plug-in to it.

It should work if the file is the same in every kepub.

Should it not first be established whether the kobo.js has any effect on reading the book on a Touch/Glo/Mini? Did anybody see a epub.kepub that did not work in any way, added then the js and can confirm that something improved?

jgoguen · 03-11-2013, 01:06 PM

I had a report on Github that it does work. If anyone wants to confirm this or demonstrate that this actually doesn't work, it would be good to have more than one person's report.

tshering · 03-11-2013, 01:14 PM

Quote:

Originally Posted by jgoguen

I had a report on Github that it does work. If anyone wants to confirm this or demonstrate that this actually doesn't work, it would be good to have more than one person's report.

I would really like to see one example that shows that the js does anything!

BobC · 03-11-2013, 02:51 PM

Quote:

Originally Posted by tshering

I would really like to see one example that shows that the js does anything!

I see that the js file is named "kobo-android.js" which just might be a clue that it is only used by the Android version of Kobo's reader as used, for instance, on Tablets rather than the Linux based Ereaders. Same goes for the "kobo-android.css" file also found in some Kepubs.

BobC

jgoguen · 03-11-2013, 05:07 PM

Now that is interesting, I wonder if they pack different files for the different apps. The file that I was given (and since discarded) was simply named "kobo.js". Does anyone have a kepub downloaded by the Kobo Desktop app to their reader that can check?

BobC · 03-11-2013, 05:54 PM

Quote:

Originally Posted by jgoguen

Now that is interesting, I wonder if they pack different files for the different apps. The file that I was given (and since discarded) was simply named "kobo.js". Does anyone have a kepub downloaded by the Kobo Desktop app to their reader that can check?

Although I do have an Android Tablet it's incompatible with the Kobo app so all the Kepubs I have downloaded have either been via the Desktop or using Wi-Fi on the touch itself. I've checked through them to find a title (they are all free) and both The Return of Sherlock Homes by Conan Doyle and The Secret Agent by Joseph Conrad have the "android" js and css files. Both books are Gutenberg sourced by Kobo.

HTH

BobC

tshering · 03-11-2013, 06:38 PM

The few kepubs that I have are all downloaded via the Desktop Application. The all contain kobo.js. They date from January 2012. The function turnOnNightMode seems to make no sense for the Touch. Functions like goBack(), goForward() seem to be so basic that it is hard to imagine how the reading engine (provided that it is depending on these js functions) can handle those things if the kobo.js is not included, and it certainly does.
Note: I cannot see any copyright notice concerning these js-files.

BobC · 03-11-2013, 07:25 PM

FWIW I have now done a diff on a kobo-android.js and a kobo.js extracted from different books. The files are identical. Both 5,506 bytes.

Looks like it's just a naming issue. It might be an interesting exercise to cobble up a kepub with some Javascript in it to see if the Touch/Glo's rendering engine actually can execute Javascript.

BobC

jgoguen · 03-11-2013, 07:26 PM

Under Canadian copyright law, so far as I understand it, as a party to the Berne Convention no copyright notice is needed as required by the "copyright must be automatic" clause. I'm not a lawyer, that's my interpretation, but if I'm right that would mean that very similar restrictions are in place for all other Berne Convention signatories, which is a respectable portion of the world. As far as I'm aware, again my own interpretations, the default copyright applied if not otherwise declared is "All Rights Reserved", which prohibits redistribution.

tshering · 03-12-2013, 05:08 AM

Quote:

Originally Posted by tshering

I just wanted to share that the kepub rendering engine does not like this kind of url-encoding. I did not test it, but this encoding might probably create the same problems with a normal epub.

It seems epub don't have problems with this encoding.

03-11-2013, 06:38 PM	#162
tshering Evangelist Posts: 413 Karma: 111714 Join Date: Jun 2012 Device: kobo touch	The few kepubs that I have are all downloaded via the Desktop Application. The all contain kobo.js. They date from January 2012. The function turnOnNightMode seems to make no sense for the Touch. Functions like goBack(), goForward() seem to be so basic that it is hard to imagine how the reading engine (provided that it is depending on these js functions) can handle those things if the kobo.js is not included, and it certainly does. Note: I cannot see any copyright notice concerning these js-files. Last edited by tshering; 03-11-2013 at 06:44 PM.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Downloading kepub to ADE	scr212	Kobo Reader	14	10-14-2012 02:37 PM
KePub Toolbox	Thasaidon	Kobo Reader	1	08-08-2012 07:49 AM
What will happen/I gain if I forced an ePub book to a KePub book?	andsoitgoes	Kobo Reader	4	04-04-2012 04:33 PM
Touch Any hack/work-around to sync bookmarks of non Kobo ePub (kepub)	andsoitgoes	Kobo Reader	3	04-03-2012 03:56 PM
Kobo Adobe Epub is a Kepub instead	rashkae	Kobo Reader	61	01-13-2012 06:15 AM

03-11-2013, 10:04 AM	#151
tshering Evangelist Posts: 413 Karma: 111714 Join Date: Jun 2012 Device: kobo touch	Yesterday I got an epub and converted it to a kepub.epub. The device did not remember the last opened page and opened the book always with the first page. When I navigated via the TOC menu, annotations and highligths did not show and it was not possible to insert new ones. This was caused by the url-encoding of the filenames in the toc.ntx. The filenames followed the pattern "CR!Ssomething_split_000.html", whearas the references in the toc.ntx followed the pattern CR%21S_split_000.html". After changing "%21" to "!" everything went fine.

03-11-2013, 12:31 PM	#155
jgoguen High Fantasy Bibliophage Posts: 183 Karma: 100000 Join Date: Jan 2013 Location: New Brunswick, Canada Device: Kobo Glo	Oh, sorry about that Looks like something I should make sure the plugin handles... since I'm in there editing stuff anyway.

03-11-2013, 01:06 PM	#157
jgoguen High Fantasy Bibliophage Posts: 183 Karma: 100000 Join Date: Jan 2013 Location: New Brunswick, Canada Device: Kobo Glo	I had a report on Github that it does work. If anyone wants to confirm this or demonstrate that this actually doesn't work, it would be good to have more than one person's report.

03-11-2013, 05:07 PM	#160
jgoguen High Fantasy Bibliophage Posts: 183 Karma: 100000 Join Date: Jan 2013 Location: New Brunswick, Canada Device: Kobo Glo	Now that is interesting, I wonder if they pack different files for the different apps. The file that I was given (and since discarded) was simply named "kobo.js". Does anyone have a kepub downloaded by the Kobo Desktop app to their reader that can check?

03-11-2013, 07:25 PM	#163
BobC Groupie Posts: 163 Karma: 21034 Join Date: Dec 2008 Location: Lancashire, U.K. Device: BeBook 1 (x2), Kobo Glo, Various Android Apps on JellyBean Tablet	FWIW I have now done a diff on a kobo-android.js and a kobo.js extracted from different books. The files are identical. Both 5,506 bytes. Looks like it's just a naming issue. It might be an interesting exercise to cobble up a kepub with some Javascript in it to see if the Touch/Glo's rendering engine actually can execute Javascript. BobC

03-11-2013, 07:26 PM	#164
jgoguen High Fantasy Bibliophage Posts: 183 Karma: 100000 Join Date: Jan 2013 Location: New Brunswick, Canada Device: Kobo Glo	Under Canadian copyright law, so far as I understand it, as a party to the Berne Convention no copyright notice is needed as required by the "copyright must be automatic" clause. I'm not a lawyer, that's my interpretation, but if I'm right that would mean that very similar restrictions are in place for all other Berne Convention signatories, which is a respectable portion of the world. As far as I'm aware, again my own interpretations, the default copyright applied if not otherwise declared is "All Rights Reserved", which prohibits redistribution.


Advertisement Enthusiast