Skip to main content
Inspiring
January 2, 2018
Answered

Font not in Bookerly

  • January 2, 2018
  • 2 replies
  • 2860 views

Hi,

I know HTML and CSS pretty well but this one is throwing me. I'm proofing my epub in MS Edge browser, the Kindle Preview and downloading as a .mobi for the Kindle. For some reason my Bookerly font is being ignored. In Edge is reverts to Times and in the Kindle I noticed it is defaulting to the 'Publisher's Font', which is some sans serif font. Yet the Kindle Preview on the kindlepreview website IS showing Bookerly. Of course I can change it in the Kindle but I want it to default to Bookerly. The CSS in idGeneratedStyles_0 is:

@11220649-face {

font-family:Bookerly, serif;

font-style:normal;

font-weight:bold;

src : url("../font/Bookerly-Bold.ttf");

}

etc etc

As you can see it references the font folder one level above, and this contains the correct Bookerly .tff files. At no point is any other font declared in my CSS (I've searched all CSS files in Dreamweaver for 'font-family'). Each page references different CSS files but none of them call up any other font. Page two displays Bookerly so I checked the code for both the HTML  and the CSS and there is nothing breaking the code. I've additional xtra.css included in my .epub but that doesn't reference any font.

Is this a known issue with either InDesign (doesn't seem to be as the HTML makes sense)? Should I strip out all font references for the Kindle to display in Bookerly by default? I don't want to do that because if people choose to read it in other readers I'd like it displayed in Bookerly. Maybe Kindle always defaults to something other than Bookerly? That doesn't make sense though.

Any tips/pointers to ensuring Bookerly is the preferred font?

This topic has been closed for replies.
Correct answer unknownsailor

Hi guys,

OK, I found the culprit at 2am this morning. It was a corrupt font file. I hadn't bothered to check the font files when breaking out the epub folder but did so on a whim and there it was. Happy to report that this was the last problem I was dealing with so I was able to go ahead and submit my book to Amazon, and it has been accepted and published! Very happy with the whole process, considering I only started teaching myself InDesign last week

Thanks to you both for your assistance.

2 replies

unknownsailorAuthorCorrect answer
Inspiring
January 3, 2018

Hi guys,

OK, I found the culprit at 2am this morning. It was a corrupt font file. I hadn't bothered to check the font files when breaking out the epub folder but did so on a whim and there it was. Happy to report that this was the last problem I was dealing with so I was able to go ahead and submit my book to Amazon, and it has been accepted and published! Very happy with the whole process, considering I only started teaching myself InDesign last week

Thanks to you both for your assistance.

FeAle-7IZsBx
Participating Frequently
January 5, 2018

Hi,

Did you change to ePUB 3 in this last export?

Regards

Inspiring
January 5, 2018

I did. Didn't appear to make any noticeable difference to the html structure but I didn't examine it closely.

BobLevine
Adobe Expert
January 2, 2018

Edge is not the tool I'd be using to check this but, is that an bookerly and opentype font?

Inspiring
January 2, 2018

It shouldn't matter, Bob, because I've declared it in my CSS. The same thing is happening when downloaded as a .mobi onto my Kinde though.

BobLevine
Adobe Expert
January 2, 2018

It might matter. What format is the font? If it's not opentype, I strongly recommend trying a font that is just to test it.