[Hitch]

Originally Posted by AppleTard

Okay, let me explain exactly what I'm doing.

I'm using Calibre to convert an HTML file to Mobi, using the option to give me a dual Mobi file (it generates a .mobi file). Then I use the "Send to Kindle" app in order to upload the file to Amazon cloud, and make it available on all my devices (the main advantage of using this process, specially since it also syncs your location and everything).

As far as I know, the only dual-mobi that is created by Calibre is the AZW3. The "mobi" is KF7, which has no KF7 features, nor font embedding, etc. Only the KF8 "mobi" (in Calibre-speak, the AZW3) has the 3 internal files--the source, the KF7 and the KF8. That's why the "mobi" file generated by Calibre will upload at Amazon (KF7) and the AZW3 won't; because the formatting is simpler, and less likely to incur issues. Above and beyond the format incompatibility, that is. Now, as I said previously--NOT a Calibre expert, but that's been my understanding. So, from the get-go, I'm not clear on what you're doing, because what you're saying is not in agreement with my understanding. I thought that the AZW3 is the KF8, with the multiple-files inisde the MOBI and the KF8 features; and the MOBI is simply essentially a PRC file. No?

Unless, when YOU say, "Dual MOBI," you mean the AZW3? But...that can't be, because you can't be emailing that successfully to the Kindle email address. Hmph.

BTW, I know that you can't send a calibre-generated azw3 file through Amazon's app, that's why I have to generate the dual mobi.

Yeah, which is where my comprehension goes south, the "Calibre-mobi as dual mobi" thing.

From my Kindle Voyager, I download the file from the cloud. Since the Voyage is KF8-compatible, that's the format Amazon sends to my device. And at this point, the font-family information is stripped, thus losing my monospace formatting.

Sorry, which "cloud?" You mean, the storage for your Kindle account, as though it's a document? So, you're using the Amazon email system, sending it out as a DOC (this is how the Amazon system sees it--as a personal doc, not a book), and then you're downloading it either via USB or..? I don't believe that you're getting a KF8 mobi.

Now, I'm perfectly willing to say I'm likely wrong--hopefully Kevin or one of the others will clarify what the MOBI is that's being built, but I thought that unless you directly side-loaded the AZW3 from Calibre, via Calibre, to a Kindle device--that once you put Amazon in the middle-all you get is a KF7 mobi, effectively, a PRC file. Which would mean no fonts, no advanced formatting.

If I use Calibre to create an old-format Mobi (KF7, I think?), and send it through the app, the font-family information is not stripped, and I get a properly formatted file. However, I lose the KF8 features.

Well, don't see how that can be, either, because KF7 can't/doesn't carry font information. Can't embed fonts, for MOBI/KF7. Did you try to call a particular font, from the CSS/HTML, that is already on the Voyage? Or...? Can you give us a screenshot of the font-enabled MOBI (KF7 mobi) that you're loading to the Voyage that's retaining fonts?

EDIT: Amazon's process is truly byzantine. I tried using Kindlegen to generate a mobi file from the HTML source. I sent the resulting mobi through the app, and it stripped the font-family. Then I used Calibre to convert the HTML to an ePub, and then ran that ePub on Kindlegen. Uploaded it and, presto! No stripped fonts. Anyway, this process is too cumbersome, and I have no idea why it works...

The KDP frequently, especially since April, strips fonts. It's a known issue. Amazon opened Pandora's box when they enabled fonts through KF8 in the first place, and they've been dialing it back ever since. It's not really byzantine; but it's hard to keep up with if you don't do it every day.

Anyway--I'm going to wait for one of the Calibre-literati to jump in here, because my understanding is that you literally can't be doing what you're doing, so I must be mistaken.

Hitch