conversion question

[holdit]

A bit wet around the ears here and have a question as I want to take an rtf document, open in Calibre and convert to an e pub and a mobi. I know how to do this but I need to know two things.

If I want my epub to have the same styling as the rtf document ( it uses the Times New Roman family) I tried to edit metadata / look and feel/ embed font family and chose Times New Roman and it did not work. How do I add css properties to the file so the epub displays inTimes New Roman font?

Second question, AM I right that I cannot embed font in a .mobi?

thank you

HH

[pdurrant]

Originally Posted by holdit

If I want my epub to have the same styling as the rtf document ( it uses the Times New Roman family) I tried to edit metadata / look and feel/ embed font family and chose Times New Roman and it did not work. How do I add css properties to the file so the epub displays inTimes New Roman font?

Second question, AM I right that I cannot embed font in a .mobi?

1. You almost certainly don't want to do that. Why do you want to impose your choice of body text font on your reader?

2. Fonts cannot be embedded in Mobipocket format ebooks. They can be embedded in Amazon's KF8 format ebooks ('azw3').

[Agama]

Originally Posted by holdit

How do I add css properties to the file so the epub displays inTimes New Roman font?

Bearing in mind pdurrant's reply, if you do still want to do this:

On the Look & Feel tab of conversion, in Extra CSS, use: body { font-family:"Times New Roman" }

(This should work without any embedding since Times New Roman is such a standard font.)

[dgatwood]

Originally Posted by pdurrant

1. You almost certainly don't want to do that. Why do you want to impose your choice of body text font on your reader?

It's perfectly reasonable for an EPUB book to set a font. There's a well-established standard for how these sorts of things are supposed to behave in the HTML/CSS world:

For fonts and other choices that can reasonably be overridden by client stylesheets (in this case, the reader's stylesheet), specify them as you normally would.

By default, the client stylesheet should not override these choices. The client's default font (for files that have no font specified) should generally not be set using stylesheets, but if your client must do so for some reason, it should do so by checking for a font on the HTML tag or BODY tag, and if no font declaration exists, setting one.

If the user asks to use a specific style instead of the publisher-provided style, the client should add a user style that takes precedence over the page style.

If you (the publisher) have a specific style that must not be overridden by the reader (e.g. for special headings that should not be treated like body text), specify !important for that style. The client should never use !important in its user style, so this should never be overridden.

Any deviation from that behavior should be considered a serious bug in the client. Similarly, using !important for styles that aren't really important should be considered a serious bug in the book.