And to round off this subject, it's possible to embedd fonts for Kindle devices. First export the EPUB file from InDesgn with the fonts embedded. After generating the EPUB file, crack it open (I use Oxygen XML Editor or Author XML Editor for this). Simply delete the 'encryption.xml' file located within the META-INF folder. Then you must replace all the fonts within the Fonts folder with the unencrypted versions. The fonts within the EPUB file are enctypted, so they cannot be read.

That's all there is to it. Open the file with Kindle Previwer and you will see the fonts in use. Keep in mind that iBooks overrides some HTML tags with the font selected by the reader, so your embedded fonts won't work for all text on that plattform. For example <h1> tags work, but <p> tags don't.

Most importantly, don't do this unless you own the font, have purchased a font license, or are using an font that allows you to freely embed it.

Good luck!

I generally recommend not to embed fonts. Not all fonts look good on screen, and not all are going to scale well to a greyscale eInk reader or a smartphone display. If you want to embed a font to achieve a particular design, you must test the book on a variety of platforms. On the other hand, there is one case in which embedding a font is critical: foreign languages. Adobe Digital Editions and the Sony Reader have poor out-of-the-box support for diacriticals and other foreign characters in their default fonts. You may also run into trouble with non-Roman character sets. If your book is absent its accent marks or contains lots of w??rds miss?ng le??ers, you’re going to need to embed a font.

There are basically two main reasons to embed fonts into an EPUB file:

• Design: The book designer has chosen a particular font to reflect the style and content of the work.
• Content: The document has particular characteristics that require a specific font.

The emerging EPUB 3 format (yet to be supported by most eBook readers) supports two font formats — OpenType and WOFF — to accommodate both traditional publishing workflows and emerging Web-based workflows. EPUB 3 also supports both obfuscated (new method) and regular font resources for both OpenType and WOFF font formats. Support for obfuscated font resources is required to accommodate font licensing restrictions for many commercially-available fonts. Note that font obfuscation and the Adobe font embedding method are different. When eBook readers finally support EPUB 3, you will be able to embed fonts into an EPUB file (using font obfuscation) and expect to see the same fonts used on every device that supports EPUB 3.

Here is a web page describing WOFF fonts: https://webfonts.info/wiki/inde&#8230;..ebfonts%3F

When you embed fonts purchased from Adobe into an EPUB file using their encryption method, you (in most cases) won't be breaching your font license. However, since it's possible that a few fonts in the Adobe Font Folio might not allow font embedding, I recommend you double-check this with Adobe to avoid any possible legal consequences. Here is the information you need to learn more about Adobe's font End User License Agreement.

Font Permission List: https://www.adobe.com/type/brow&#8230;..enses.html

Font Embedding Permissions: https://www.adobe.com/type/brow&#8230;..dding.html

As for fonts that ship with Microsoft Windows 7, they are governed by the same restrictions as the products they are supplied with. You are not allowed to copy, redistribute or reverse engineer the font files. Some fonts may be embedded within document files. Embedded fonts can only be used to print, preview and in some cases edit the document in which they are embedded. For more details see the license agreement supplied with the product. Here is more information about font redistribution and licensing: https://www.microsoft.com/typog&#8230;../faq11.htm.