Amazon Guidelines

More documents

Recommendations

Info

Publishing on Kindle: Guidelines for Publishers Chapter 2 Chapter 3 Subchapter 1 Subchapter 2 Chapter 4 Subchapter 1 Section 2 Using CSS classes: div.chapter { margin-left: 1em} div.subchapter { margin-left: 2em} Section 1 Chapter 1 Chapter 2 Chapter 3 Subchapter 1 Subchapter 2 Chapter 4 Subchapter 1 Section 2 3.8.2 Styling Guideline #2: Format Sidebars Correctly When inserting sidebar content into the main flow of a book formatted for Kindle Format 8, use float via CSS. However, if the book is formatted for Mobi 7, use the HTML tags before and after the sidebar to differentiate it from the main body of text. Avoid using negative em values when specifying dimensions for a float element. 3.9 HTML Guidelines 3.9.1 HTML Guideline #1: Constructing Well-Formed HTML Documents (XHTML) Kindle Format 8 supports most HTML 5.0 features, although the following HTML features are not fully supported: forms, frames, and JavaScript. When creating source HTML or XHTML for the Kindle, refer to one of the following books as a primer on constructing well-formed HTML documents: HTML, XHTML, and CSS by Elizabeth Castro (published by Peachpit Press): http://www.amazon.com/HTML-XHTML-and-CSS/dp/B000SEFC5Q Beginning HTML with CSS and XHTML: Modern Guide and Reference by David Schultz and Craig Cook (published by Apress): http://www.amazon.com/Beginning-HTML-CSS-XHTML- Reference/dp/B001D25ZPE Beginning Web Programming with HTML, XHTML, and CSS by John Duckett (published by Wrox): http://www.amazon.com/Beginning-Programming-HTML-XHTML-ebook/dp/B000VZQVVG 3.9.2 HTML Guideline #2: Anchors Must Be Added Before Formatting Tags Correct: Chapter 1 Incorrect: Chapter 1 3.9.3 HTML Guideline #3: EPUB Guide Items Are Optional Guide items are an optional feature in the EPUB format. Kindle provides support for the cover, TOC, and text guide items. 3.9.4 HTML Guideline #4: Using Single Column Layout and Avoiding Absolute Positions Create the content using single column layout and avoid using position:absolute for alignments. 3.9.5 HTML Guideline #5: Using position:absolute for Text on Image For text on an image that needs to be positioned exactly, use the position:absolute attribute. Only use this attribute for books that need a fixed layout. Kindle Publishing Guidelines Amazon.com 22
Publishing on Kindle: Guidelines for Publishers 3.9.6 HTML Guideline #6: Avoid Using Negative Em Values Avoid using negative em values for positioning text and margins. 3.9.7 HTML Guideline #7: Avoid Using Scripting with SVG Images Scripting is not supported. All scripts are stripped from the source during conversion. SVG with animation is not supported. 3.9.8 HTML Guideline #8: Avoid Using Negative Values for Line Height Do not use negative values for the line-height attribute. They are not supported. 3.10 Embedded Font Guidelines Kindle Format 8 supports custom embedded fonts within the eBook. These fonts can be either Open Type or True Type font (OTF, TTF). Type 1 (Postscript) fonts are not supported. For size considerations, Amazon recommends that the publisher only include the font faces used in the book, instead of the entire font set. The default set of fonts in the Kindle Readers have been tuned for quality. Publishers do not need to include the Charis font with their content. The font files within the book are obfuscated to reduce the probability of reuse, but it is the responsibility of the publisher to secure the appropriate license rights for the fonts. 4 Creating Fixed-Layout Children’s and Comic Books Certain books have elements that are fixed in size, should not reflow, and should not allow fonts to be resized. For example, children’s books and graphic novels have full-page images with text positioned precisely over the image. To accommodate these media types, KF8 introduces new metadata fields and guidelines. Fixed-layout books do not support reflowable text and should only be used when the entire book is fixed layout. To demonstrate best practices in creating fixed-layout books, Amazon provides a children’s book example at www.amazon.com/kindleformat (under the KindleGen Examples heading). This example is a demonstration of how to create content to take advantage of fixed layout and Region Magnification. It is not intended to be an HTML tutorial. 4.1 Metadata Fields Supporting Fixed-Layout Books These metadata fields are specified in the OPF file. Each of these values applies to the entire book. For a demonstration, see the children’s book example at www.amazon.com/kindleformat (under the KindleGen Examples heading). Metadata Description Required. Identifies the book as a fixed layout. Valid values are “true” or “false”. The default value is “false”. Required. Identifies the original display size the content was designed for. The screen resolution can have any positive integer value. Required. Locks the orientation of the content to either portrait or landscape. Valid values are “portrait” or “landscape”. The default value is “portrait”. Optional. Provides additional reader functionality, specific to the classification of the book. Valid values are “children” or “comic”. Optional. Some devices can magnify portions of the text. To enable this functionality, specify “true”. Valid values are “true” or “false”. The default value is “false”. Kindle Publishing Guidelines Amazon.com 23
Page 1 and 2: Amazon Kindle Publishing Guidelines
Page 3 and 4: Publishing on Kindle: Guidelines fo
Page 5 and 6: 1 Getting Started Publishing on Kin
Page 11 and 12: 3.1.7 Text Guideline #7: CSS Suppor
Page 13 and 14: 3.3 Table of Contents Guidelines Pu
Page 17 and 18: Description Image Bad quality: The
Page 21: Publishing on Kindle: Guidelines fo
Page 27 and 28: Fixed-layout sample page Example:
Page 37 and 38: 8 Media Queries Publishing on Kindl
Page 41 and 42: 8.3.2 Option 2: Using Different CSS
Page 45 and 46: 11 Appendices Publishing on Kindle:
Page 51 and 52: CSS Attribute Supported on Kindle e
Page 53 and 54: CSS Attribute Supported on Kindle e
Page 55: • E: before • E: after • E::b

Amazon Guidelines

Create successful ePaper yourself

Delete template?

Save as template?