Hyperlink underlines and custom fonts

[djprescott]

Hi all

I wonder if you could help me out.

I have two issues: one being the removal of underlines on hyperlinks and the other being using custom fonts.

I have an ePub file that works fine and looks exactly as it should. However, when I convert to mobi through the Amazon previewer, the underlines are re-introduced and the custom fonts fall away.

Does anyone have any suggestions for what I should check?

Thanks in advance
Dan

[HarryT]

The Mobi format does not support embedded fonts. Use KF8 instead.

[djprescott]

Hi there. If I'm running it through the amazon kindle converter, would it not automatically convert to KF8?

[DiapDealer]

Originally Posted by djprescott

Hi there. If I'm running it through the amazon kindle converter, would it not automatically convert to KF8?

It would actually create a master file that contains BOTH a KF8 version and a MOBI version (along with the original source). The capabilities of the device/app you're viewing the finished product with (or the device emulation mode you're using in Kindle Previewer) will determine if you see the KF8 or the MOBI version.

If you're viewing the output with a device/app that doesn't support KF8, you're going to see the MOBI version of the book (which doesn't support embedded fonts, and requires quite a bit of hoop-jumping to create a link that isn't underlined). Same goes if you've chosen a device-mode in Kindle Previewer that emulates a device which doesn't support KF8.

[HarryT]

You also (on a real Kindle, at least) need to select the "Use Publisher Fonts" option in order to enable the use of the embedded fonts in a book.

[JSWolf]

Originally Posted by HarryT

You also (on a real Kindle, at least) need to select the "Use Publisher Fonts" option in order to enable the use of the embedded fonts in a book.

That is just a rather bad option default. The embedded fonts should be on by default and turned off to not have them displayed.

[HarryT]

Bad or not, that's the way it is .

[DiapDealer]

A bad default option is better than no option at all. The newer Kindle Fire HDs simply ignore any embedded fonts if they're assigned to the 'body' element via CSS (even though Kindle Previewer's FireHD emulation mode indicates everything's hunky-dory). There simply IS no option to "use publisher fonts" on those devices. Embedded fonts for headers and special sections of text still work as expected, but they're making it harder and harder for ebook creators to dictate the standard paragraph font. And if you do succeed in dictating the standard paragraph font on those devices, you've effectively taken away the user's ability to change the font without hacking the ebook.

[djprescott]

Thanks all.

So there is no reason why my embedded fonts should fall out simply through the process of Kindle conversion? Presuming I am then viewing the file on a KF8 device?

@DiapDealer. You mention about newer kindles not recognising custom fonts used in 'body' elements. Is there a workaround for this do you know?

[HarryT]

It's a really, REALLY bad idea to change the body font of a book, because it prevents the user from using their own choice of font. Presumably this is the reason that the FireHD blocks it.

[djprescott]

Thanks for you reply.

What are your thoughts on changing the fonts in headers etc?

I can understand having the body font flexible for the user, but I really would like to use custom fonts in headers etc

Custom fonts inside <h#> tags should be accepted should they?

[HarryT]

Custom fonts in headers are absolutely fine, and yes, they should work OK.