Documentation
Elements
- <a>
- <altRepresentation>
- <aside>
- <assessment>
- <author>
- <backcover>
- <blockquote>
- <body>
- <bodymatter>
- <caption>
- <code>
- <cover>
- <dd>
- <dl>
- <document>
- <dt>
- <em>
- <figure>
- <figureGroup>
- <frame>
- <frontcover>
- <frontmatter>
- <hd>
- <img>
- <indicators>
- <input>
- <jacketcopy>
- <legend>
- <li>
- <line>
- <linegroup>
- <list>
- <meta>
- <metadata>
- <note>
- <noteRef>
- <p>
- <pagebreak>
- <poem>
- <publication>
- <pullquote>
- <rearmatter>
- <section>
- <source>
- <span>
- <sub>
- <subtitle>
- <sup>
- <table>
- <tbody>
- <td>
- <tfoot>
- <th>
- <thead>
- <title>
- <tr>
Image properties
See img and figureGroup for more information about image elements.
Image quality
Deliver images in high quality, 300 DPI for raster graphics (i.e. low compression) JPG format.
Deliver image content maintaining a level of 100% integrity to the source material in terms of:
- Colour images – images are required to be reproduced with no observable degradation in colour rendering.
- Greyscale images – images are required to be reproduced without introducing visible compression artefacts, e.g. banding.
- Text rich images – images in the work containing a lot of text, e.g. flow charts, are required to be reproduced without introducing any degradation in legibility in comparison with the original.
Image size
Image size must correspond with the size of the image in the source material, with exception for the following:
- An increase in the size of an image is required to achieve the legibility of text rich images, see “Image quality” above.
- Maximum image size is set to 800 pixels on the longest side of the image for images with landscape orientation.
- Maximum image size is set to 800 pixels on the longest side of the image for images spread over more than one page.
Image format
Format images as [production-ID]_[pagenum]-[number of image on that specific page].jpg. Use three digits for pagenum. For example: 320066_p009-1.jpg. Over a 1000 pages, use four digits for pagenum. For example: 320066_p0009-1.jpg.
Format cover as "cover.jpg".
Filename rules
In addition to the filename pattern above, every image filename must follow a few universal rules. These rules prevent broken references between the XML and the actual files on disk, the single most common cause of missing images in a production.
- Lowercase only. Use lowercase letters for the entire filename, including the extension. Write
image1.jpg, notImage1.jpgorimage1.JPG. - No spaces. Replace a space with an underscore or hyphen. Write
chapter_opener.jpg, notchapter opener.jpg. - No accents, parentheses, or other special characters. Use only letters
a–z, digits0–9, and the characters-,_,.and/. - The
@srcin the XML must match the actual filename exactly, including case. On our Linux production servers filenames are case-sensitive, soImage1.jpgandimage1.jpgare considered two different files. Local Windows workstations hide this issue — the broken reference only surfaces downstream.
Why case matters
Windows is case-insensitive, opening Image1.jpg works even if the real file is image1.jpg. Linux is not. Our production and conversion pipeline runs on Linux, so a mismatch that passes silently on a local machine will break at the point where it is hardest to catch. Keeping every filename and every @src value in lowercase is the simplest way to guarantee the two match.
Automated checks
The MONET Schematron enforces these rules automatically. Three checks flag problems in image references: img-src-lowercase, img-src-case-consistency, and img-src-suspicious-chars. See the Schematron quality checks page for details.
Image positioning
Images covering two or more pages
If an image covers two or more pages, do not split the image. Instead, process as a single image. Place the image on the page containing the initial instance of the image.