Hi,
It appears that the header (see the earlier image) uses variable byte length values (see the getVariableWidthValue in mobi_index.py in KindleUnpack). Each obviously human readable string is preceded by its length (stored as a variable width value).
I think to properly reverse this thing we would need to have someone disassemble the new code from the update that adds kfx support. From that we may be able to figure out the meaning of each field, how the exact keys are generated (etc).
My 2 cents ...
KevinH
|