[KevinH]

Hi,

Okay, I can recreate this with KindlePreviewer and Jerome.mobi.

The problem is that if I unpack Jerome.mobi and the mobi8-Jerome.mobi and compare the content.opf files and the contents of the oth_tbl (which is used to build the guide elements), they are identical (byte for byte).

So something inside the mobi8 only version must indicate the presence or absence of a toc that we do not know about. Perhaps one of the fields that we don't know in the mobi8 header or something in the damn FLIS, FCIS, or DATP.

This is going to be a real bugger to find.

KevinH

Originally Posted by KevinH

Hi DiapDealer,

Please e-mail me your problem test case. I split both Jerome.mobi and the Cherokee language testcase.mobi and then unpacked the mobi8 only version of each and in the guide section of the content.opf there is indeed the proper toc pointing to the right file.

Is there someplace other than the guide section of content.opf that needs to be properly set to allow it to find its toc?

For the KF8 part, all of the guide is stored in the oth_tbl and my tests show it properly there in both versions.

For the old mobi sections, the guide info is stored inside the rawml file and just needs to be copied to the right place in the content.opf

Thanks,

KevinH