View Single Post
Old 04-12-2011, 11:06 AM   #22
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,804
Karma: 6000000
Join Date: Nov 2009
Device: many
Quote:
Originally Posted by Hitch View Post
Except for the fact that--unless Kovid has addressed this--Calibre-generated MOBI's are not readable on any "Kindle for X" device, because Calibre-generated MOBI's do not have adequate space in the headers to accommodate the second layer of encryption required for a file to be read on anything other than the device. Calibre is a library system, and a damn fine one, but it is NOT a production tool for professional production (for Kindle books for SALE).

HTH
Hitch
Hi Hitch,

Could you please be very specific about what extra header information is needed ... is this simply the extended header info where metadata is stored on mobi ebooks or something else? As far as I know, all Kindle DRM ebooks store part of the information needed to decode the DRM in extended header metadata values. Is this what you are referring to? If something else, can you please supply the specifics of what you need.

I am sure it would be quite easy to make a mobi to mobi converter that adds in an extended header with whatever fields you need added to the extended header and in whatever order you want them.

KevinH
KevinH is offline   Reply With Quote