Answers.Body: <p>First, though you can embed fonts in an epub/mobi file, there is no guarantee that the reading system will display the font correctly. I used an embedded font on my last ebook, and it did not render correctly on all devices (on kindle for example, it rendered on most systems, but not all). My guess is that more recent reading systems will support embedded fonts better, but you should always assume that a backup font could be used. </p>
  
  <p>Most reading systems offer a limited amount of fonts and allow the reader to override the publisher's specified fonts. In some reading systems, there is an option for the system to use publisher settings, but there is no guarantee that the reader will have checked this setting. </p>
  
  <p>My strategy has been to not specify fonts for the body text, but specify/embed fonts only when the element needs to be differentiated from the rest of the text. (Maybe it's a blockquote, a heading or a preface or title). </p>
  
  <p>I haven't tested ebooks in a while, but you might find it surprising to know that certain fonts don't display properly  when embedded on some reading systems while other fonts do. You can only determine this by testing on several different reading systems. </p>
  
  <p>When the user changes the font on the reading system, usually it's only for body and paragraphs; sometimes it's for paragraphs and headings. It depends on the reading system. Some reading systems (like Adobe Digital Editions on android) embed all the fonts and don't give readers any choices, while other reading systems let you choose from 20 or 30 different fonts.  This is insanity, don't you agree? </p>
  
  <p>As a publisher, it drives me crazy that a reader would switch fonts because of a  personal preference. I predict that eventually readers won't have the option to select font family -- only font size --, but I admit I really don't know what will be the future.  </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-25T12:57:30.007Z
Answers.Text: As a reader It drives me mad if I can't set things so I can actually read the text. If the publisher locks things down I won't buy as I physically cannot read for example see kindle open dyslexic font.
Answers.UserDisplayName: mmmmmm
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-16T21:28:47.833Z
Answers.LastActivityDate: 2017-03-16T21:28:47.833Z
Answers.UserDisplayName: idiotprogrammer
Answers.Body: <p>"As a publisher, it drives me crazy that a reader would switch fonts because of a personal preference" If they prefer it in another style I'm not sure why that would bother you. It would bother me more if my customer found my work easier to digest in another font but couldn't change it. Why on earth would you make your book harder to read?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-09T08:22:26.853Z
Answers.LastActivityDate: 2017-10-09T08:22:26.853Z
Answers.UserDisplayName: user10071
Answers.Body: <p>There isn't much you can do, if the device allows to change the fonts and the user is willing to use that option, he will do it.</p>
  
  <p>If you use different fonts not just for aestethics, but with a functional purpose (i.e. to display code with a fixed width font, or to differentiate quotes from default paragraphs, and so on), your best option, IMHO, is to insert a disclaimer where you explain this to the end user.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-17T17:21:08.260Z
Answers.Text: Totally right. On the Title page, I sometimes will indicate a one or two line to turn on publisher defaults. But some of the lesser ebook apps strip out publisher defaults entirely!
Answers.UserDisplayName: idiotprogrammer
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-17T13:43:35.313Z
Answers.LastActivityDate: 2017-03-17T13:43:35.313Z
Answers.UserDisplayName: Sekhemty
Answers.Body: <p>You <em>can't</em> generalise, because there are many e-book reader programs, and all of them work differently.</p>
  
  <p>In the <strong>Calibre e-book reader program</strong>, for instance, the user can design a personal stylesheet, which is an optional choice by the user. That is a user-customisable stylesheet which, if present, will over-ride all the css settings embedded in the e-book (in so far as they conflict with the stylesheet).</p>
  
  <p>The reader program is <em>designed</em> to be able to over-ride the fonts specified in the ebook file in this manner, in case the user <em>doesn't</em> have those fonts on his device.</p>
  
  <p>There is an option open to the ebook <em>publisher</em> : embed the fonts in the file. Then the user doesn't have to provide for not having them. But it does make the e-book file <em>much</em> bigger, which can be very inconvenient for the user. Many devices are slow, and under-powered. </p>
  
  <p>The future gives all the advantage to the user. The user-groups will deliberately ensure that this is so. This is called freedom of choice.</p>
  
  <p>What the publisher can do is provide the most user-friendly experience possible. This includes NOT issuing huge files, stuffed with obscure fonts that slow down the user's ability to scroll through the e-book.</p>
  
  <p>Proprietory fonts are not welcome if they have a negative impact on the end-user. Learn to do things in a user friendly way, so that the user has no motivation to override the e-book's default settings.</p>
  
  <p>Real books, made of paper, generally use only a small number of industry-standard fontfaces. This should also be the practice with e-books.</p>
  
  <p>Develop industry standards for e-book files, and for e-reader devices, to improve compatibility between the books and the reader program.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-22T20:45:20.413Z
Answers.LastActivityDate: 2019-02-22T20:45:20.413Z
Answers.UserDisplayName: Ed999
Body: <p>What happens if I have used 2 different fonts in my content for mobi/epub and user changes the font in the devise,like in kindle?
  does both the fonts change? if yes, is there any way to protect the fonts from changing(apart from  converting to images)?</p>
  
Tags: <epub><mobi><font-rendering>
Title: What happens if I have used 2 different fonts in mobi/epub and user changes the font in the devise?
UserDisplayName: Amol Patil
ThreadText: # What happens if I have used 2 different fonts in mobi/epub and user changes the font in the devise?
  
  (Asked by: username_0 on 2017-03-16)
  
  What happens if I have used 2 different fonts in my content for mobi/epub and user changes the font in the devise,like in kindle?
  does both the fonts change? if yes, is there any way to protect the fonts from changing(apart from converting to images)?
  
  **Tags:** epub, mobi, font-rendering
  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_1 on 2017-03-16. Score: 2 | Accepted answer
  
  First, though you can embed fonts in an epub/mobi file, there is no guarantee that the reading system will display the font correctly. I used an embedded font on my last ebook, and it did not render correctly on all devices (on kindle for example, it rendered on most systems, but not all). My guess is that more recent reading systems will support embedded fonts better, but you should always assume that a backup font could be used.
  
  Most reading systems offer a limited amount of fonts and allow the reader to override the publisher's specified fonts. In some reading systems, there is an option for the system to use publisher settings, but there is no guarantee that the reader will have checked this setting.
  
  My strategy has been to not specify fonts for the body text, but specify/embed fonts only when the element needs to be differentiated from the rest of the text. (Maybe it's a blockquote, a heading or a preface or title).
  
  I haven't tested ebooks in a while, but you might find it surprising to know that certain fonts don't display properly when embedded on some reading systems while other fonts do. You can only determine this by testing on several different reading systems.
  
  When the user changes the font on the reading system, usually it's only for body and paragraphs; sometimes it's for paragraphs and headings. It depends on the reading system. Some reading systems (like Adobe Digital Editions on android) embed all the fonts and don't give readers any choices, while other reading systems let you choose from 20 or 30 different fonts. This is insanity, don't you agree?
  
  As a publisher, it drives me crazy that a reader would switch fonts because of a personal preference. I predict that eventually readers won't have the option to select font family -- only font size --, but I admit I really don't know what will be the future.
  
  > **Comments:**
  > **username_2**: As a reader It drives me mad if I can't set things so I can actually read the text. If the publisher locks things down I won't buy as I physically cannot read for example see kindle open dyslexic font.  
  
  ---
  
  ### Answer by username_3 on 2017-10-09. Score: 3
  
  "As a publisher, it drives me crazy that a reader would switch fonts because of a personal preference" If they prefer it in another style I'm not sure why that would bother you. It would bother me more if my customer found my work easier to digest in another font but couldn't change it. Why on earth would you make your book harder to read?
  
  
  ---
  
  ### Answer by username_4 on 2017-03-17. Score: 3
  
  There isn't much you can do, if the device allows to change the fonts and the user is willing to use that option, he will do it.
  
  If you use different fonts not just for aestethics, but with a functional purpose (i.e. to display code with a fixed width font, or to differentiate quotes from default paragraphs, and so on), your best option, IMHO, is to insert a disclaimer where you explain this to the end user.
  
  > **Comments:**
  > **username_1**: Totally right. On the Title page, I sometimes will indicate a one or two line to turn on publisher defaults. But some of the lesser ebook apps strip out publisher defaults entirely!  
  
  ---
  
  ### Answer by username_5 on 2019-02-22. Score: 1
  
  You *can't* generalise, because there are many e-book reader programs, and all of them work differently.
  
  In the **Calibre e-book reader program**, for instance, the user can design a personal stylesheet, which is an optional choice by the user. That is a user-customisable stylesheet which, if present, will over-ride all the css settings embedded in the e-book (in so far as they conflict with the stylesheet).
  
  The reader program is *designed* to be able to over-ride the fonts specified in the ebook file in this manner, in case the user *doesn't* have those fonts on his device.
  
  There is an option open to the ebook *publisher* : embed the fonts in the file. Then the user doesn't have to provide for not having them. But it does make the e-book file *much* bigger, which can be very inconvenient for the user. Many devices are slow, and under-powered.
  
  The future gives all the advantage to the user. The user-groups will deliberately ensure that this is so. This is called freedom of choice.
  
  What the publisher can do is provide the most user-friendly experience possible. This includes NOT issuing huge files, stuffed with obscure fonts that slow down the user's ability to scroll through the e-book.
  
  Proprietory fonts are not welcome if they have a negative impact on the end-user. Learn to do things in a user friendly way, so that the user has no motivation to override the e-book's default settings.
  
  Real books, made of paper, generally use only a small number of industry-standard fontfaces. This should also be the practice with e-books.
  
  Develop industry standards for e-book files, and for e-reader devices, to improve compatibility between the books and the reader program.
  
  
  ---
  
  