Hi Kovid,
Quote:
Originally Posted by kovidgoyal
If that's the case, I'm really surprised at Amazon. Do they lack the ability to write a simple script to insert space into a MOBI record0 and update the offsets table accordingly. calibre has been able to do that for *years*.
Oh well, I'll have the next release of calibre guarantee that there is always 8KB worth of null bytes immediately after the exth header in record0, when creating MOBI files and when updating mobi metadata.
|
I am not sure if that is the reason or not. All of this is just a guess on my part! And one I can't even test since I do not publish on Amazon (or anywhere else!).
Assuming that encoding a book with DRM is costly on a large scale, I would only encrypt each book once and then have extra space in record 0 where I could write the real encryption key encrypted with a set of PIDs and the metadata values needed to figure out at least one of those PIDs based on information stored on the device itself, and my own registration information, as well as metadata information taken from the book itself.
Then a simple rewrite of section 0 can handle all devices/apps/readers and not changes need be made.
As you said, it is very easy to redo the offset tables so all of this might just be a waste of time!
KevinH