Thread: KindleUnpack (MobiUnpack): Extracts text, images and metadata from Kindle/Mobi files
View Single Post
Old 11-08-2013, 02:19 PM   #632
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by DiapDealer View Post
I would suggest a quick and dirty test to make sure that changing the KF8 EXTH data in the hybrid mobi/KF8 even has the desired effect on Kindle devices (when unsplit).

With regard to the PDOC/EBOK cdetype (EXTH 501), there would need to not only be a way to change the record but also to add the record entirely. Because so far as I can tell, Kindlegen/Previewer doesn't create the 501 EXTH record in the output it creates in the first place. That record doesn't get added until delivery from Amazon to a user's device.
Diap:

Clarify for me: why are we doing this in the first place? I don't mean to be dense, and admittedly just skimmed over most of this, but...what's the point?

Hitch
Hitch is offline   Reply With Quote