0% found this document useful (0 votes)

75 views4 pages

14.2 Text Guidelines Dictionary Entry Template

This document provides guidelines for publishing dictionaries on Kindle, including: 1) Metadata should specify the input and output languages, and primary index name. For bilingual dictionaries, the input language code identifies the source language and output code the target language. 2) Dictionary entries should have a clean format with the headword first, definition, and horizontal rules between. Images and tables are discouraged. 3) Dictionaries must use a single-column Mobi 7 format and include an <mbp:frameset> element wrapping all <idx:entry> elements. 4) Each entry is marked by <idx:entry> tags and includes the indexed <idx:orth> headword and possible

Uploaded by

Alojaa

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

75 views4 pages

14.2 Text Guidelines Dictionary Entry Template

Uploaded by

Alojaa

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 4

Publishing on Kindle: Guidelines for Publishers

<DefaultLookupIndex> tags in the OPF file also should appear as the value of the name
attribute in the <idx:entry> elements in the content of the dictionary (see section 14.3.3).
As an example, for a Spanish-French dictionary, the input language code would be es; the output
language code would be fr, and the primary index might be named Spanish. A list of country codes can
be found at: http://www.w3schools.com/tags/ref_language_codes.asp.

Example: (Bilingual Dictionary Metadata)

<x-metadata>

<DefaultLookupIndex>Spanish</DefaultLookupIndex>

...

</x-metadata>

For a monolingual dictionary, the same language code must appear twice: once to identify the input
language, and again to identify the same language as the output language. To identify a regional variant
for the source and/or target languages, a regional suffix may be appended to the ISO 639-1 code. For
example, en-gb indicates British English, while en-us indicates US English.

Example: (Monolingual Dictionary Metadata, Regional Variant)

<x-metadata>

<DefaultLookupIndex>headword</DefaultLookupIndex>

...

</x-metadata>

14.2 Text Guidelines Dictionary Entry Template

A simple, clean format works best for in-book lookup. Amazon recommends these dictionary content and
formatting features for a high-quality user experience:
The headword (word being defined) should come first in the entry, and should be
distinguished from surrounding content (on its own line, flush left, in bold).
Every dictionary entry should contain a definition (or translation, for bilingual dictionaries).
Horizontal rules should appear between each entry.
Each alphabet letter section should begin on a new page.
Images should be avoided (see section 9.4 for image constraints).
Tables should not be used (see section 9.5 for table constraints).
Font color, size, and typeface should not be forced (see section 9.3 for text guidelines).

Kindle Publishing Guidelines Amazon.com 72

Publishing on Kindle: Guidelines for Publishers

14.3 Basic Dictionary HTML

14.3.1 Format
Dictionaries for Kindle must be in Mobi 7 format, not in KF8. For this reason, the dictionary layout should
use a single-column format. Multiple columns and sidebars are not supported in Mobi 7 format.

14.3.2 Frameset Element

All dictionaries must have an <mbp:frameset> element as the first child of the <body> element. This
frameset element contains all of the <idx:entry> elements of the dictionary.

The namespace for this <mbp:frameset> element is

xmlns:mbp="https://kindlegen.s3.amazonaws.com/AmazonKindlePublishingGuideline
s.pdf" and it must be declared in the root <html> element of the XHTML document.

Example:
<html xmlns:math="http://exslt.org/math" xmlns:svg="http://www.w3.org/2000/svg"
xmlns:tl="https://kindlegen.s3.amazonaws.com/AmazonKindlePublishingGuidelines.pdf"

xmlns:saxon="http://saxon.sf.net/" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:cx="https://kindlegen.s3.amazonaws.com/AmazonKindlePublishingGuidelines.pdf"
xmlns:dc="http://purl.org/dc/elements/1.1/"

xmlns:mbp="https://kindlegen.s3.amazonaws.com/AmazonKindlePublishingGuidelines.pdf"
xmlns:mmc="https://kindlegen.s3.amazonaws.com/AmazonKindlePublishingGuidelines.pdf"
xmlns:idx="https://kindlegen.s3.amazonaws.com/AmazonKindlePublishingGuidelines.pdf">

<head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head>

<body>

<mbp:frameset>

<idx:entry name="english" scriptable="yes" spell="yes">

<idx:short><a id="1"></a>

<idx:orth value="aardvark">

<idx:infl>

<idx:iform value="aardvarks"></idx:iform>

</idx:infl>

</idx:orth>

A nocturnal burrowing mammal native to sub-Saharan Africa that feeds exclusively on ants and termites.

</idx:short>

Kindle Publishing Guidelines Amazon.com 73

Publishing on Kindle: Guidelines for Publishers

</idx:entry>

</mbp:frameset>

</body>

</html>

14.3.3 Headword Index

In order to make an alphabetical index of headwords, it is necessary to use special tags that are not
standard HTML. The source still will be valid XHTML with these added <idx> mark-ups.

<idx:entry>..</idx:entry>

The <idx:entry> tag marks the scope of each entry to be indexed. In a dictionary, each headword with
its definition(s) should be placed between <idx:entry> and </idx:entry>. Any type of HTML may be
placed within this tag.

The <idx:entry> tag can carry the name, scriptable, and spell attributes. The name attribute
indicates the index to which the headword belongs. The value of the name attribute should be the same
as the default lookup index name listed in the OPF. The scriptable attribute makes the entry
accessible from the index. The only possible value for the scriptable attribute is "yes". The spell
attribute enables wildcard search and spell correction during word lookup. The only possible value for the
spell attribute is "yes".

Example:
<idx:entry name="english" scriptable="yes" spell="yes">

The <idx:entry> tag also may carry an id attribute with the sequential id number of the entry. This
number should match the value of the id attribute in an anchor tag used for cross-reference linking:

Example:
<idx:entry name="japanese" scriptable="yes" spell="yes" id="12345">

The entry id number is not used for in-book lookup; instead, the wordform entity to be indexed for lookup
must be contained in the <idx:orth> element as described in the following sections.

<idx:orth>..</idx:orth>

The <idx:orth> tag is used to delimit the label that will appear in the index list and that will be
searchable as a lookup headword. This is the text that users can enter in the search box to find an entry.

Example:
<idx:orth>Label of entry in Index</idx:orth>

Kindle Publishing Guidelines Amazon.com 74

Publishing on Kindle: Guidelines for Publishers

Here is an example of an extremely simple entry that could be part of an English dictionary. From this
example code, the word "chair" would appear in the index list and would be searchable by users.

Example:
<idx:entry>

<idx:orth>chair</idx:orth>

A seat for one person, which has a back, usually four legs, and sometimes two arms.

<idx:entry>

The value attribute can be used on the <idx:orth> tag to include a hidden label in the entry. This
attribute maintains lookup functionality in the presence of the special formatting that commonly appears
on headwords in dictionaries.

Example:
<idx:orth value="Hidden Label of entry in Index">Display format</orth>

If the headword should be displayed in the dictionary with a superscripted number to indicate
homographs, with a registered trademark symbol, with middle dots to separate syllables, or with any other
added symbols, this special formatting should appear on the text between the <idx:orth> tags, but not
on the text in the value attribute. The text in the value attribute should match exactly the form to be
used for lookup. If a value attribute is not supplied, then the entity between the <idx:orth> tags will be
indexed for lookup. If middle dots, superscripted numbers, or any other symbols are included in the text
between the <idx:orth> tags, then in-book lookup will fail unless a hidden label with the lookup form is
supplied in the value attribute.

Example:
<idx:orth value="Amazon"> 3</orth>

If the dictionary uses more than one orthographic script, then the format attribute on the <orth> tag
can be used to identify each script for building the index.

Example:
<idx:orth format="script name">

Along with this primary index of headwords for all entries in the dictionary, in-book lookup also requires a
supplementary index of inflected forms for each headword. To build the hidden inflection index, additional
data should be nested within the <idx:orth> tag as follows.

14.4 Inflections for Dictionaries

Dictionaries should be built so that multiple inflected forms of a single root word all access the same
entry. A complete list of inflected wordforms should be provided for every headword. If an entry uses
multiple orthographies, then separate inflections must be provided for each orthography.