View Single Post
Old 04-15-2011, 04:56 PM   #27
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,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Quote:
Originally Posted by kovidgoyal View Post
I think what's happening is the set MOBI metadata code in calibre is truncating record 0 to the minimum possible size. You can confirm this by not using save to disk to get the MOBI out of the calibre library.
Yes, you are correct.

Here are the output sections starting offsets if I simply manually copy the .mobi file out of the Calibre Library.

Unpacking Book ...
number of sections 354
0 2912
1 5364
2 6548
3 7612
4 8676
5 9736
6 10799
7 12194
8 14307

So in this case Section 0 starts at 2912 and ends at 5364 for a size of exactly the 2452 bytes you said it would be.

Perhaps the Amazon reject came because of using "Save to Disk" which made the exth region so tight there was not enough space to easily change it without rewriting the entire actual file.

My guess is they keep exactly one binary DRM image of each book and write the EXTH info on the fly to correspond to the version of Kindle you have (K4Mac, K4PC, etc) in order to encode the PID information needed for that reader/platform/device.
KevinH is offline   Reply With Quote