[Hitch]

Originally Posted by GJ Coop

Well, no.

I have not yet succeeded with getting the font to embed despite changing to a couple of different Google Webfonts, that's .ttf fonts. One font became distorted so it looked like the hanging letters were dripping down the page in the .mobi in the desktop previewer, might have been tears, or blood. OK, for a crime book, I guess.

I decided to cut my losses and create the title page as an image.

That was easy enough for me to do, and simplifies the number of embedded font classes in the code from six to two. One for the Table of Contents, the other for the chapter headings.

Six, quite frankly, is a LOT. We've done them, but I always recommend against that many fonts. First, size is a real issue. Secondly, it's just...a lot. {shrug}. Something is wrong in your coding. I don't know what, but you can't be quite THAT unlucky with font selections. I think you said you used Calibre, right? I/we don't, so there may be something happening there that affects it. Pure speculation on my part, but...

I added the not particularly elegantly named font, YanoneKaffeesatz-Regular, to the Manifest:



Added the @font-face to the CSS



Added the tags to the text:



The .mobi created by the desktop app looks good in all the previewers, so once again my fingers are crossed that it will be acceptable when it pops out on the other side in the Amazon Kindle Store Previewer.

Good luck. Seriously.

I guess I could get someone else to do this for me but I really want to nut this process out myself. I am writing short travel style ebooks and there is scope for writing plenty more of them, actually a whole new career and I'm 99% of the way there with the first four ebooks.

I'll report back on how KPD has machinated the .mobi. It might just work this time.

You might want to consider getting a pro to do it once, so you have a template of a book that works. Just an idea. Most of the better pros use the same CSS in their ePUB that they do in their MOBI, because they're building the mobi from the ePUB. It would give you a starting point.

FWIW, in the CSS:

src: url(../Fonts/YanoneKaffeesatz-Regular.ttf);

try:

src: url("../Fonts/YanoneKaffeesatz-Regular.ttf") format("truetype");

Quotes around the source url, and add the format text.

And for this, in the manifest:

media-type="application/x-font-truetype"/>

(Does that validate? Really?)

Try this:

media-type="application/x-font-ttf" />

I know that this seems like nitpicky little stuff, and I know you're trying to build a mobi, but that type declaration shouldn't be validating in ePUBcheck, firstly, and you never know...it might be messing with your mobi, too. You never know--never--what's going to set off the KDP. I spent hours yesterday working out a process diagram of all the myriad ways we've worked with the SRL (Start Reading Location) and Fonts, and all the fail paths versus the success paths. Trust me when I say, the fail paths are far more numerous than the succeed paths. And it's always something teeny. OR ridiculous.


Hitch