Quote:
Originally Posted by rashkae
Just idle speculation on my part. There was an issue a long time ago where Kepubs were being loaded to the Adobe content server instead of epubs. They were encryted with Adobe DRM, but once decrypted, the files were formatted as Kepubs (with the javascript Kobo uses to define several css styling elements, and the infamous missig space after italics throughout the text.). It was my understanding, possibly wrong, that files delivered from the Adobe content server are provided by the publisher (or more specifically, their chosen e-distributor.. Ingram?) This makes me wonder if the Kepubs themsevles are actually created by the publisher/distributor as well, and no in house by Kobo.
|
The normal epub is added to the platform of the e-distributor(s) in a certain (language) territory by the publisher and normally contains either Adobe DRM or a watermark protection and is available to all member reselling partners. Meaning the book is "provided as is" by the publisher. The publisher is responsible for all content errors.
Larger booksellers can get access - on a individual basis - to the source files to add their own DRM-scheme. Or as in de case of Kobo also add additional code to make the books fully functional with their device specific features. At least that's theory and is how it should supposed to be but in reality doesn't pan out very well for Kobos proprietary kepub format. It influences too much with the original layout of a book (which you don't necessarly have to like) beyond the activation of specific device features.
And I'm quite sure that most publishers and authors are not aware this.
See this article in Dutch. It also mentions Kobo and iBooks.
Nieuwe eBoekafnemers: Bruna.nl en Yindo