Quote:
Originally Posted by Hitch
So: the problem appears solved, then? Is that the takeaway?
Hitch
|
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.
I added the not particularly elegantly named font, YanoneKaffeesatz-Regular, to the Manifest:
Quote:
|
<item href="Fonts/YanoneKaffeesatz-Regular.ttf" id="Yanone Kaffesatz" media-type="application/x-font-truetype"/>
|
Added the @font-face to the CSS
Quote:
@font-face {
font-family: "Yanone Kaffeesatz";
font-style: normal;
font-weight: normal;
src: url(../Fonts/YanoneKaffeesatz-Regular.ttf);
}
h1 {
text-align: center;
margin: 0;
padding: 0;
color: #e65c00;
font-size: 100%;
}
.title {
font-family: "Yanone Kaffeesatz", sans-serif;
page-break-before: always;
}
|
Added the tags to the text:
Quote:
|
<h1><span class="title">Day 7 | Brinkley Bluff: on top of the world</span></h1>
|
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.
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.