HDX Publisher's Font Doesn't Work

[Blossom]

Has anyone figure out how to get the publisher's font or embedded fonts to work on the Kindle Fire?!?

I've had hopped this would be fixed. If you know of a free book that does work let me know so I can look at the code and figure this out.

Publisher's font works fine on other Kindles but not the Kindle Fires.

Originally Posted by Blossom

Has anyone figure out how to get the publisher's font or embedded fonts to work on the Kindle Fire?!?

I've had hopped this would be fixed. If you know of a free book that does work let me know so I can look at the code and figure this out.

Publisher's font works fine on other Kindles but not the Kindle Fires.

It doesn't work in the Kindle for iOS app either. I'm not sure about the Kindle for Android app, but it probably doesn't work there either. It is strange how Amazon cripples the reader functions. I'm not sure if they do it on purpose or just out of stupidity.

Since I read on my PW2 and my iPhone/iPad, I have to modify books to have bold text. Embedded fonts are nice on the PW2, but as noted they don't work on the Kindle for iOS app.

[Blossom]

Hot Diggity Dog! I got it work! *dances around the room in her PJs* It's crazy the things that come to you when about to drift off to sleep. There still is no publisher's on/off but the font is showing. It can't be changed but I don't want to change it so it works for me! Wheeee!!!

Okay deep breath. Fonts must be reference by file name not family name. Internal family name wont work. That's what Calibre does it adds the internal family name when it should be the filename instead!

[beckywc]

Can you explain what you did, thanks.

Originally Posted by Blossom

Hot Diggity Dog! I got it work! *dances around the room in her PJs* It's crazy the things that come to you when about to drift off to sleep. There still is no publisher's on/off but the font is showing. It can't be changed but I don't want to change it so it works for me! Wheeee!!!

Okay deep breath. Fonts must be reference by file name not family name. Internal family name wont work. That's what Calibre does it adds the internal family name when it should be the filename instead!

That is how I reference them for my PW2--by file name. One file for each set of glyphs (Normal, Italic, Bold, and BoldItalic). But I always use Sigil. (I hate the calibre conversions for various reasons.) But with the PW2 we have the Publisher Font option. Without that option then you are forced to always read in whatever font the publisher embeds! Yuk!!!! I would want to turn that off when the publisher picks a terrible font, and they probably will. Maybe the Publisher Font option is hidden in some menu setting somewhere. You might check the Fire manual.

Here is how I do it in Sigil but I have no clue if this works on the Fire HDX. It works well on the PW2. BTW, you can also use negative left/right margins in the CSS to narrow the margins on the PW2. Can they be used on the Fire HDX too?

@font-face {
  font-family: "CharisSILSpecial";
  font-weight: normal;
  font-style: normal;
  src: url("../Fonts/CharisSILBold-Regular.ttf");
}

@font-face {
  font-family: "CharisSILSpecial";
  font-weight: normal;
  font-style: italic;
  src: url("../Fonts/CharisSILBold-Italic.ttf");
}

@font-face {
  font-family: "CharisSILSpecial";
  font-weight: bold;
  font-style: normal;
  src: url("../Fonts/CharisSILBold-Bold.ttf");
}

@font-face {
  font-family: "CharisSILSpecial";
  font-weight: bold;
  font-style: italic;
  src: url("../Fonts/CharisSILBold-BoldItalic.ttf");
}

body { font-family: CharisSILSpecial }

[Blossom]

Originally Posted by jswinden

That is how I reference them for my PW2--by file name. One file for each set of glyphs (Normal, Italic, Bold, and BoldItalic). But I always use Sigil. (I hate the calibre conversions for various reasons.) But with the PW2 we have the Publisher Font option. Without that option then you are forced to always read in whatever font the publisher embeds! Yuk!!!! I would want to turn that off when the publisher picks a terrible font, and they probably will. Maybe the Publisher Font option is hidden in some menu setting somewhere. You might check the Fire manual.

I remove the publisher's fonts in Calibre before it goes on my eReaders that's never a problem. The wonderful thing is I can read with my own font now!

What manual it didn't come with one.

[Blossom]

Originally Posted by jswinden

Here is how I do it in Sigil but I have no clue if this works on the Fire HDX. It works well on the PW2. BTW, you can also use negative left/right margins in the CSS to narrow the margins on the PW2. Can they be used on the Fire HDX too?

Scratch all that! It can have spaces and it doesn't matter what the family name is the big problem lies in the body tag. Calibre uses it's own class and the HDX doesn't recognize it. It's so simple to fix though!

In Extra CSS box on its conversation window you just has to specified the font family. Like this

p {font-family: "Trebuchet", sans-serif;}

That would cause Calibre to put the font family in every class that contains text!

Body class will not work.

[Blossom]

Originally Posted by beckywc

Can you explain what you did, thanks.

All you do is go to embed the font like you would on a eInk Kindle book in Calibre then on the Extra CSS box put"

p {font-family: "Trebuchet", sans-serif;}

Be sure to modified it to your font. In this case Trebuchet is the font name. The sans-serif/serif isn't really needed. You can omit it to look like:

p {font-family: "Trebuchet";}

The downside is you are stuck with the font. You can't turn it off at all but if you only read with one font this isn't a problem.

[Blossom]

Good news!

Kindle Previewer has just been updated for the HDX!! It's quite accurate too. This is so much better than having to load and reload books on the HDX to see if they look right.

Originally Posted by Blossom

Good news!

Kindle Previewer has just been updated for the HDX!! It's quite accurate too. This is so much better than having to load and reload books on the HDX to see if they look right.

I use Kindle Previewer for all my conversions and never seem to have the issues I hear about with calibre. I highly recommend it. I like that it gives you a compile log so you can see if anything didn't go as planned. Sometimes a file path is wrong within the HTML of the book, and that helps you trace it down quickly and resolve the issue. Debugging someone else's HTML and ePubs can be a PITA, but this makes it easier.

[Blossom]

Originally Posted by jswinden

I use Kindle Previewer for all my conversions and never seem to have the issues I hear about with calibre. I highly recommend it. I like that it gives you a compile log so you can see if anything didn't go as planned. Sometimes a file path is wrong within the HTML of the book, and that helps you trace it down quickly and resolve the issue. Debugging someone else's HTML and ePubs can be a PITA, but this makes it easier.

I use Calibre due to having to edit each book but I can now see how it will look on the HDX. Before I was having to transfer to book to the HDX look at it then delete it and try again till it look right. Now I can use Kindle Previewer instead.

[Xanthe]

Kindle Previewer:

http://www.amazon.com/gp/feature.html?docId=1000765261