Quote:
Originally Posted by pdurrant
I think these must be the bytes that were messing up the first version of the Mobipocket decoder, and that the second version tried to fix without really understanding them.
|
Indeed -- I'm not sure the community as whole really understands them. Calibre's rules for parsing them look to be the same as mobidedrm 0.5's, except that Calibre will ignore the extra data flags field if the MOBI header is shorter than 0xe4 bytes or *longer* than 0xe8 bytes. I vaguely recall being responsible for the test case which led to that one, but I'm now suspecting it may have been an interaction with an earlier version of mobidedrm. And neither handles bit 1 of the extra data flags, although Calibre will when Kovid gets around to pulling from lp:~llasram/calibre/staging
.
Quote:
Originally Posted by pdurrant
It would be very nice to get the controlling bits and format of the trailing bytes set out clearing in the wiki...
|
I've got a whole ream of stuff I figured out writing oeb2mobi that I need to add to the wiki... The effect of bit 1 of extra data flags, the format of "uncrossable" boundary records, the format of the FCIS record, and the format of the index records (although I'm still working on that...).