Quote:
Originally Posted by tompe
The code is not removed so it is in the packed data (I just checked). Does it work with mobigen?
|
It does work with mobigen. The issue that the Mobipocket renderers (well, Mobipocket Reader Desktop 6.2 anyway) don't actually use the markup to find uncrossable boundaries. Instead, they use a "trailing data item" appended to the end of each text-content record. The details are:
- The MOBI header version field(s) must be >= 6.
- The MOBI header extra data flags field must have 0x4 set.
- Each text record has a trailing data item in the standard form (<data><size>, where <size> is a Mobipocket variable-length encoded integer and includes the size of <size>).
- The data consists of a running index of the offsets of uncrossable boundaries, represented by a series of variable-length encoded integers.
- The value of each integer is the offset from the position specified by the previous entry (or the beginning of the record for the first) to the last byte of the boundary tag (the '>' character) and right-shifted 3 bits. The "previous offset" for each entry is not the exact previous offset, but the actually-encoded offset & ~0x7.
I'm actually not 100% sure about the "last byte of the boundary tag" business, but that's how it seems to work. I'm planning to add this plus a few other things I've figured out to the MOBI page on the wiki at some point.
-Marshall