Quote:
Originally Posted by JLuecking
I did a factory reset and I went back to the previous firmware. I blame the bug onto the calibre plugin.
|
Possible, but considering that it also happens with some Kobo-provided KePub files I doubt it. Either that or books with my plugin are broken the same way as some Kobo-supplied KePub files.
Quote:
Originally Posted by Ken Maltby
So somewhere up north, something (the opposite of a Gnome) is reading this thread, in his little log cabin software programing Gulag, and chuckling "You didn't think you could get away with using OUR reading program on your dirty little FAKE Kepubs, did you!!" "Get it through your heads, it's Kobo purchased Ebooks or Bugger off."
|
Did you consider that Kobo may not be telling us what's needed to make a fully-compliant KePub? And why would they, when rolling our own KePub files removes incentive to purchase Kobo books? The fact that people on the Kobo development and product teams know that this plugin is working as well as it is and the worst they've done is say "we can't support you if you use this" says a lot to me. Unlike what I would have expected from some other companies, Kobo hasn't even tried to do anything to discourage me from trying to figure out the KePub details and for that I think they deserve a lot more respect than what your post implies. Yes, Kobo needs a lot of work on their development processes. With that said, don't assume that code issues implies lazy/bad/malicious/whatever developers, or that process issues are the fault of the developers' managers.
Besides, Kobo intends for user-supplied books to use the Adobe renderer; the KePub plugin causes books that were never intended to be parsed to be uploaded using a program that was never intended to upload KePub files and accessed using a renderer that end users are never intended to access in this manner.