JS file about calibre-kobo-driver HOT 5 CLOSED

It's hard to tell, even re-reading the Copyright Act of Canada. It seems that all the discussion of software is around removing Digital Restrictions Management (DRM) with no distinction made between software or any other copying method anywhere else.

I think, under sections 29.21 and 29.22 (http://laws-lois.justice.gc.ca/eng/acts/C-42/page-19.html), that I'm OK as long as I extract the file from a Kobo-supplied kepub file without digital restrictions. To me, there isn't any distinction between that and simply having the file waiting to be copied, but apparently there is.

from calibre-kobo-driver.

I'm not a lawyer, so what I'll say is not 100% sure, but I'm reasonably sure that it can be a way to avoid problems.

My idea is:
a function added to the plug-in, something like "add files to the ebook" with no reference to kobo files, this function simply points to one or more files whatever they are, and adds them to every kepub created.

So the choice to take a free kepub from kobo, extract the JS and CCS files, and sue them for home made ebooks will be of the final user completely.
The plug-in would offer only a generic function, without any relation to kobo protected material.

Sorry for my english, hope is clear what i wrote.

from calibre-kobo-driver.

It's clear, but the way I read the Copyright Act it says that I have to use an existing work. So I would need to start with an existing book in its entirety. It would be nice if I were wrong on that, just copying in a file would be a lot easier than extracting a file that has different names in different book files, but copyright law tends to make life hard for the end user.

from calibre-kobo-driver.

I thought that the JS file is the same identical file for every kepub from kobo, if so, merely adding it sould be enough, but if i'm wrong then of course my idea is useless. I should make some experiment manually adding it to see what appens.

from calibre-kobo-driver.

You also have to add a reference to the script in the code, and maybe some other things as well. My current code has just a reference to the file, and for some books it works and others it actually makes the problem worse. So I'll need to take apart a Kobo book in some more detail, but I'm a good part of the way there.

And the file is identical in the books I've looked at so far, but the name of the file isn't always the same. It looks like the name matches .*/?kobo.*\.js$ based on what I've seen.

from calibre-kobo-driver.