Quote:
Originally Posted by eschwartz
To elaborate: calibre does not have the ability to update the metadata within the AZW3 component of an existing dual-MOBI (type "both"). This is due to the difficulty of robustly modifying the metadata headers in a dual-MOBI.
Kovid hasn't devoted the time to fix this, since it basically only affects people who email to their Kindle and want to receive AZW3 via the PDOC service. Which is a very small percentage of users, and it is simply not worth investing the time it would take to create and test a fix.
|
That makes sense -- but I'm still not seeing the expected behavior. I've set "old" in preferences, and deleted the MOBI copy locally, and deleted the Amazon copy, and re-sent via email, which prompts conversion... and still no plugboard result.
Looking more closely, I'm wondering if this is a clue. In the conversion log, I see:
Code:
Creating MOBI Output...
Serializing resources...
Splitting markup on page breaks and flow limits, if any...
Splitting on page-break at id=calibre_pb_0
Splitting on page-break at id=calibre_pb_1
Split into 3 parts
Creating KF8 output
Generating KF8 markup...
Compressing markup...
Creating indices...
Creating MOBI 6 output
Applying case-transforming CSS...
Parsing manglecase.css ...
Rasterizing SVG images...
Converting XHTML to Mobipocket markup...
Serializing markup content...
Compressing markup content...
Generating MOBI index for a book
MOBI output written to C:\Users\Laird\AppData\Local\Temp\calibre_185vi_\tsnb7r.mobi
...despite:
Should it be creating KF8 and MOBI 6 if the option is set to "old"? Might that be related to what I'm seeing?