Typesetting using the Well-Formed Document Workflow requires that certain standards are maintained, facilitating the best use of the features available in the Scribe Tools for InDesign, the ability to output both print and web PDFs, and the ability to export content for review and to produce documents in other formats.
Typesetting Basics
Typesetting using the Well-Formed Document Workflow requires that certain standards are met, even if the typesetter does not have access to the Digital Hub or Scribe Tools for InDesign.
The typesetting instructions presented here require familiarity with industry standard terms and programs, specifically Adobe InDesign. The Typesetting Basics documentation applies to all, including freelancers, while additional information is provided for typesetters and designers with access to Scribe’s tools.
Preparation and File Importing
Typesetting should always begin with a scribed file that has been converted to InDesign Tagged Text (IDTT) in the Digital Hub. Do not import .docx files, as this can introduce overrides and bypasses the benefits of Hub-generated IDTT.
Text Flow
All frames (text boxes) in the main text flow should be threaded together. This excludes sidebars, tables, figure captions, and other floating elements. The Scribe Tools for InDesign used to export content rely on a single text flow (what InDesign refers to as a story) in order to anchor images and other disconnected elements. It is preferable (but not necessary) that the project be typeset in one file, rather than separate files for each chapter, to help later conversions run more efficiently.
Pagination
Front matter pages should use roman numerals. Body pages should use arabic numbers.
Praise pages and galleries may use letters to assist with navigation, though these numbers typically would not appear on the pages for a reader to see.
Breaking Pages
Valid ways to break pages include building breaks into a style’s keep options, adjusting the text frames to force text onto the next page, and adding page break characters. When using the page break character, place it at the end of the preceding paragraph and not on its own line. If a blank page is used, delete the text frame on that page and apply the “[none]” parent page. Do not include a text frame that only contains a page break character.
Style Use
All styles used must be compliant with ScML.
The WFDW allows for the customization of styles in InDesign to achieve the desired rendering for print while maintaining the structural integrity of each element.
Correct Scribing
Whether starting a design, a full typeset, or applying corrections, confirm that the content is scribed correctly and consistently.
Examples include the following:
- Styles with no default definition should be used appropriately and consistently. These styles include pcust1/pcust2/pcust3, ccust1/ccust2/ccust3, wl styles, and sli.
- Use bkau1 for “edited by” and bkau for the names, as the names are the primary element on title pages.
- Sidebar (sb) and box (bx) styles should be used for content that can be considered an “aside” rather than part of the main body content.
Alt Styles
If it is necessary to adjust styles for the print book, an “alt” style variation may be used. Alt styles create rendering variation for styles in a print version that will not be structurally different in the archival ScML. If a distinction is to be retained permanently, unique ScML styles must be applied to those elements. Do not use alt styles to modify aspects of first-line indentation or space above/below settings that must be retained in all versions (print and ebook). When using the Scribe Tools for InDesign to export the content, the alt styles will map back to the original style name, thereby losing any distinction (ah-alt1 and ah-alt2 would both map back to ah).
An alt style is created by appending “-alt” to the end of any ScML paragraph style name (e.g., “pf-alt”). A typesetter/designer can create as many alt styles as are necessary as long as they follow this pattern. Commonly, numbers are used (-alt1, -alt2, etc.), but text can also be used after the trigger of “-alt” (-alt blue, -altlarger, -alt-[ANY TEXT HERE]).
Paragraph-specific Character Styles
Character styles can be adjusted to better fit with the display of certain paragraphs by adding “-[character style]” to the end of a paragraph style name within the character style sheet.
The two main use case scenarios are the following:
- Distinct font variations: If the sb paragraphs use a different base font than the main text, sb-i can be used to support the specific italic font in sb paragraphs.
- Font reversals: When the i character style is used within a paragraph style that uses an italic base font, the i style must be reversed to render with a roman font.
When using the Scribe Tools for InDesign to export the content, these will revert to the base character style (sb-i would map back to i).
Note: When building these styles, the paragraph style must be in the paragraph style sheet. The sb-i style will only map properly to i if sb is present.
Note: Paragraph-specific character styles are generated automatically by the Digital Hub’s IDTT conversion for italics in commonly used head and title styles (e.g., ct-i and ah-i).
Small Caps
Italic small caps should be constructed by skewing the small caps font (typically by 10°), rather than applying a small caps setting to an italic font.
Note: In some instances, applying small caps to an italic font will be acceptable, but in many cases the italic font weight will not match the roman text.
Undefined Styles
All undefined styles should be given a definition regardless of whether they change the text’s rendering. Even if styles like ennum or tocnum do not change the look of the text in a particular design, they should still be defined. This indicates that the typesetter/designer checked every paragraph and character style and that nothing will display improperly just because a style has no definition.
Undefined styles are displayed with a gray icon to the right of the style name in the style sheet. To ensure that everything is defined, delete all unused styles and then scroll through each style sheet to check for icons.
Text Variables
InDesign has the capability of populating fields such as running heads through text variables. Text variables can use custom text or pull from paragraph or character styles. Commonly, book titles (bk), part titles (pt), author names (bkau/au), or chapter titles (ct, ctfm, ctbm) are used.
If reference text is needed that has not already been identified with an ScML style, the rhref character style can be applied, typically defined in the style sheet not to modify the paragraph’s rendering. The rhref style is not retained when exporting content and is only used within InDesign.
Note: Text variables cannot retain a mix of character styles. If a running head needs to include both roman and italic text, for example, this should be applied directly onto a parent page.
See Endnote Page Ranges for how to set up text variables for endnote running heads.
Local Formatting
In the Well-Formed Document Workflow, all rendering (how things look) is handled through the style sheets. This includes font definition, font size, alignment, and spacing. Any local formatting added without a style will not map out for XML export. This might result in unformatted or lost text.
The exception to this is adjusting the tracking/kerning on a case-by-case basis. As a rule, paragraph style settings should include the proper tracking settings, but local overrides can be applied to help improve the typography/layout as needed.
Legacy Fonts
Legacy fonts should not be used to represent characters. A legacy font will display the letter “a” as the Hebrew aleph character, for example. The appropriate Unicode character should be used in all instances.
Hyphenation and Language Settings
Select the appropriate language in the paragraph style sheet.
Right-to-left languages, such as Hebrew, require both the language and “World-ready paragraph composer” to be selected.
Note: It is recommended that hyphenation is turned off entirely for titles and heads, as well as when representing text that would not typically hyphenate in the real world (e.g., email messages and handwritten letters).
Vertical Spacing
Vertical spacing is always handled through the paragraph styles, never through the use of hard returns (empty paragraphs). By defining the space above and below elements through styles, important information about each paragraph is retained and appropriate definitions can be set for those paragraphs in other programs.
The default approach to spacing, in conjunction with proper scribing, should be the following:
- Heads should have more space above than below
- Use space above “first” styles (e.g., bqf, slf)
- Use space above and below “standalone” styles (e.g., bqs,)
- Build space above elements rather than below for unarticulated styles that require space such as
Hard Returns and Soft Returns
Hard returns should be used for any paragraph break that needs to be retained permanently. (If a forced column break is used, this would take the place of the hard return.)
Soft returns can be used to force a word to the next line. They retain the integrity of a paragraph while forcing a line break. If a soft return is used, it should be for a cosmetic break that is only done to address typographic issues in the print edition, such as avoiding stacks or loose lines. If it is a necessary line break, then it should use a hard return, as soft returns are removed in the extraction process.
Apply soft returns after the space between words rather than replacing the space entirely. If that space is not included, the words will get run together when the soft return is removed from the exported XML.
Typesetter Spaces
Nonbreaking spaces are retained when exporting content using the Scribe Tools for InDesign.
Hair spaces, thin spaces, em spaces, and en spaces are retained as regular spaces. If hair spaces or thin spaces are used between single and double quotation marks, apply the tso character style to these spaces so that they will be deleted when exporting.
Typeset Only Styles
Typeset Only Paragraph Styles
Running head paragraphs that use the rh (running head), rhv, (running head verso), and rhr (running head recto) styles will automatically be deleted by the Scribe Tools for InDesign when exporting content.
Note: Text on parent pages is excluded from the export even if other styles are applied, but these ScML styles are recommended in order to maintain consistency across projects.
If a spacebreak paragraph (psec) occurs at the top of a page and asterisks (or a different text pattern) are used to indicate this to a reader, scribe the asterisks with tsectop or tsecbot paragraph style. This will be deleted when exporting, as the visible page break distinction is not applicable in other environments like ePub.
Note: Any paragraph style, including the text it is applied to, can be marked for deletion during the export to XML process by appending “-tso” to the paragraph style name. For example, the function of tsectop or tsecbot could also be achieved by applying sec-tso.
Typeset Only Character Styles
The tso (typeset only) character style can be used for any hair spaces, thin spaces, or other characters that may be inserted to control special spacing needs. In rare cases, if a hyphen must be typed to force a word to break at a desired point, apply tso to the typed hyphen. Any text using the tso character style will get deleted when exporting to an XML file.
The tocnum character style works in a similar fashion and ensures that page numbers are removed from the file during the extraction process, as they are not relevant in a digital environment. This style is also used in some Scribe Tools for InDesign features.
Do not apply tso or tocnum styles to any content that should be retained outside of the typeset.
The tocemb (TOC Embedded) character style can be used on the first phrase in a table of contents listing. This is typically a chapter, part, or figure number. This style is not used in scribed Word documents, but it can be added in InDesign to apply different rendering to the text and is retained when exporting content to XML.
Non-mapping Typeset Character Style
The tsnomap character style can be used in places in which a specific character style is needed for the print book but not needed in the XML file. A common usage is to apply tsnomap to the first two em dashes in a bibliography entry in order to kern three em dashes into a solid line.
When exporting to XML, the tsnomap character style is removed while the text itself is retained.
Image Requirements
See Image Management for how to use Scribe Tools for InDesign to import images and manage alt text.
Additional requirements are listed for the following:
- Image Placement
- Image Cropping
- Image Text Labels
- Color and Grayscale Images
InDesign Features
In many cases, InDesign includes multiple ways of achieving the same rendering. Some features should never be used while others should only be used if all potential pitfalls have been accounted for.
Embedded Notes
Scribe recommends using the embedded footnotes feature in InDesign. IDTT produced through the WFDW using the Digital Hub will retain embedded footnotes. In InDesign, settings can be established (e.g., renumber by page, renumber by section, use numbers, use letters, use symbols) through the menu.
Note: Footnotes can result in body text hyphenating across pages even when the style settings indicate not to allow this. This is due to InDesign recognizing only the footnotes as the end of the page.
Scribe does not recommend the use of the embedded endnote feature. Endnotes should use literal text. Options are available in Scribe Tools for InDesign to assist with renumbering endnotes should any be added or removed during corrections rounds.
Bullets and Numbering
Bullets and numbers should be literal content when typesetting in the WFDW. Content that has been generated automatically by InDesign is considered a text variable and is not included when exporting text.
Note: If InDesign’s automatic bullet feature is used, this can be addressed through CSS settings when producing ePub versions. Scribe recommends only doing this if the process is fully coordinated.
Drop Caps, Nested Styles, and GREP Styles
Rendering options can be applied using InDesign’s options for nested or GREP styles. When exporting with the Scribe Tools for InDesign, nested and GREP styles are made literal and are retained in the resulting XML output.
Rules, Shading, and Baseline Shifts
Rules, shading, and baseline shifts may be handled through the style sheet options. Information about this rendering is not retained outside of InDesign.
Layers
InDesign layers can be used to hide content from the visible output. Any layer set to be invisible will not be included when extracting content with the Scribe Tools for InDesign.
Image Management
Place images using the Scribe Tools for InDesign. When coordinated with a scribed manuscript, this enables the inclusion of alt text.
Note: If alt text is not available when a typeset begins, it can be added at any time. See the Short Description Text (Alt Text) for how to include alt text at any stage.
Image Placement
Images can be placed outside of the text flow (commonly at the top or bottom of pages) or in-line with the text.
Note: Though text wrap may be used, it can interfere with vertical justification settings in text boxes.
Images do not need to be anchored. Anchoring is permitted, but the Scribe Tools for InDesign will anchor images when exporting to XML.
Image Cropping
All images should be cropped properly before being placed in InDesign. Masking images in InDesign will only affect the PDF output. The image files themselves would remain uncropped and need to be cropped manually for an ebook version.
Handling this before typesetting ensures that the work does not need to be done twice and prevents mismatches between different versions of the book.
Image Text Labels
If a text label needs to be added to an image, this should also be done in an outside program instead of being placed over the image in InDesign.
Color and Grayscale Images
Color images can be placed in the typeset and output as grayscale when producing a print PDF. If grayscale image files are used in a print book but color versions are used for ePub or web PDF versions, organize the image files with the same file names and include the appropriate set of images when producing each output.
Resolution
Illustrations, maps, photographs, and other art should be a standard electronic format (TIFF, EPS, JPEG) at a minimum resolution of 300 dpi.
Side-by-side Images
If images need to be placed side-by-side permanently, combine them into a single image so that this arrangement will be retained. In environments like ePub, separate images would be stacked vertically.
Tables and Tabbed Content
InDesign Tables
Tables created in Microsoft Word will import as InDesign tables. Cell styles will import automatically with the names thcell, tchcell, and tdcell. Designers/typesetters can create new cell style names with any name. Cell style names are not retained when exporting content using the Scribe Tools for InDesign.
InDesign tables, including information about column spans, are retained when exporting using the Scribe Tools for InDesign. Borders and shading information are not retained.
Tabbed Content
Tabs can be used (including specialized right-align tabs) to place content on pages. Most commonly, tabs are used in tables of contents, lists, and notes.
Do not use tabs for first-line indentation or as a means to indicate levels of poetry.
Tabs are retained when exporting content with the Scribe Tools for InDesign. If proceeding to produce an ePub, tabs should be removed from the .sam file before processing to ScML. Tabs should either be deleted or replaced with a space, as needed.
Typography Standards
Scribe’s typography standards are intended to support best practices in creating files that meet WFDW requirements while also being visually appealing, enhancing the reader’s experience and comprehension. Standards can be adjusted based on the needs of a particular book or publisher preference.
Most typography standards can be established through settings in the paragraph and character style sheets along with using features available in the Scribe Tools for InDesign.
Short Lines
The text of the last line of a paragraph should run longer than the indent of the following paragraph. Short lines may consist of a single short word, two or more short words, or the final fragment of a url that is breaking over a line.
Some short lines (e.g., a two-digit number) will typically be acceptable as part of a note or bibliography entry, while it would be unacceptable at the end of a paragraph in the body of the book.
Widows and Orphans
No widows or orphans are allowed. At least two lines of text should appear on each page if a paragraph crosses a page break.
- orphan: The first or last line of a paragraph, when it appears alone on a page.
- widow: A word or short last line of a paragraph, appearing by itself at the beginning of the following page or column.
Bad Breaks
Word Breaks
- No word may break across any page.
- Hyphenated words should only break directly after the existing hyphen.
- Words connected to an em or en dash should only break after that dash.
- Words connected to an ellipsis should not hyphenate.
- A minimum of three letters is required before and after a hyphen.
- Compound words should break at root words when possible.
- Words with mixed capitalization should break at the capitalized root words.
URL Breaks
Never break URLs with a hyphen.
Break URLs:
- After a slash (unless publisher- or project-specific instructions indicate otherwise).
- Before any other punctuation, including periods, commas, question marks, exclamation points, hyphens, @ symbols, and semi-colons.
- Between long strings of letters or numbers.
Avoid breaking a URL across a page whenever possible.
If an email address must break across a line, follow the URL breaking rules.
Stacks and Rivers
- stack: Letters, words, or punctuation appearing directly above/below one another.
- river: A gap that flows between words for at least three lines.
Avoid rivers, and avoid word stacks of two words, three letters, or three punctuation marks.
Footnotes
Start a footnote on the page that references it. If possible, place the footnote in its entirety on the referencing page.
Documents should not have footnotes in tables, instead using table notes.
Heads and Titles
Keep at least two lines of text following a head at the bottom of a page.
Break heads and titles evenly or at a sensible point, such as a punctuation mark or beginning/end of a complete phrase.
Avoid hyphenating words in heads and titles.
Leading and Text Crashes
Leading should be appropriate based on text size. The leading should be larger than the font size (e.g., 10/12 or 11/13).
Text should not crash (intersect) with other text or images, either vertically or horizontally.
Tracking
For standard body paragraphs, tracking should be set to zero.
Do not adjust tracking to be looser than +20 or tighter than -20. (Depending on the font and design, +15 or -15 may be more appropriate limits.)
The total difference between adjacent lines should never be more than 30.
Image Standards
Absent specific instruction, images should be placed at the top or bottom of a page, as near to the in-text reference as possible, after that reference.
See Image Management for additional requirements and recommendations.
Table Standards
Absent specific instruction, tables should be placed at the top or bottom of a page, as near to the in-text reference as possible, after that reference.
Tables should not break across pages unless they cannot fit on a single page.
Columns that only contain numbers should center on the longest line and align on the decimal point (or the end of the whole number if no decimal point is used).
If a table breaks from a recto to a verso page, include a line saying “(continued)” on the recto page and repeat the table head on the verso page, followed by “(continued).”
See Tables and Tabbed Content for additional requirements and recommendations.
Initials
Initials should be kept together on the same line.
If there is only a first initial, keep it connected to the surname.
PDF Output
Follow the printer’s specifications when outputting PDFs at all stages.
If a printer has not yet been determined, output with PDF/X-1a, no crop marks.
Spreads
Spreads should align at the top and bottom.
Multiple columns should end evenly on individual pages and across the spread.
Pages can be run one line short or long to align spreads.
Pages can end short if necessary when the following page begins with a head.
Do not follow a short spread with a long spread; do not follow a long spread with a short spread.
Any page containing body paragraphs should include a minimum of 5 lines.
Parent Pages and Running Heads
Parent pages should be set up to include all design elements that do not need to be retained outside of InDesign, including running heads, drop folios, and decorative images that will not be included in ebook versions.
Create running heads using text variables whenever possible.
Unless otherwise specified, body page running heads should use book title / chapter title for single author books or chapter author / chapter title for books with multiple authors. Front and back matter sections should typically use the chapter title for both verso and recto pages.
Use the [None] master page for any page that is completely blank.
Typeset QC Checklist
PDF Checks
Design and Version Continuity
Check that the file is the proper trim size. (This can also be checked in the InDesign file.)
Check that the title (and other content) matches the content on the cover, if available.
Does the PDF meet the required page count?
Front matter pages should use roman numerals, and image galleries may require separate numbering.
This includes the publication date, ISBN(s), copyright data, and impression lines.
Table of Contents
Check that each entry leads to the correct page.
Check that entries in the TOC match the titles and heads in the book for wording, spelling, and terms that include character styles.
Parent Page Elements
Check for spelling, character styles, and alignment.
Check that elements such as chapter titles and parent page objects are placed consistently.
Typography
Check for widows and orphans.
Check for paragraph section breaks occurring at the top of a page.
Check for hyphenation across pages due to style settings or the presence of footnotes.
Check for bad URL breaks.
Check for bad breaks due to bracketed letters (for example, “[T]his”).
Check for social titles like “Ms.” or “Dr.” and the person’s name.
Check for initials and the rest of a person’s name.
Check for numerals along with a spelled-out number or a unit of measurement or currency (e.g., “1 billion,” “10 cm,” “100 dollars,” or “$1 million”).
Check for abbreviations like “pp.” or “no.” and the numeral that follows.
Check for names of biblical books that are preceded by a numeral (for example, “2 Corinthians” or “1 Peter”).
Check that lines do not end with list leaders.
Check for punctuation, letter, and word stacks.
Check for any loose or tight leading or kerning.
Check that long lines balance or align properly when wrapping.
Check for text crashes.
Check that numbers in lists or notes align properly for the largest amount of digits in use.
Check that illustrative elements are placed in the correct location.
Check that images appear in their entirety.
Check that heads and captions are consistently placed.
Output
Run a preflight in Adobe Acrobat to analyze the document.
Check for color vs. grayscale.
Check for proper page size and print marks.
Check for image size and settings.
InDesign Checks
Use the Scribe Tools for InDesign.
options in theStyles
Check for the proper scribing of elements.
Are “-alt” styles used for elements that should be unique styles?
All styles on parent pages (e.g., running heads and folios) should be defined through the style sheet.
Are italic reversals handled properly?
Are italic small caps skewed properly?
Check for font mismatches between paragraph styles’ base fonts and the character styles appearing within them.
Right-to-left languages, such as Hebrew, require both the language and “World-ready paragraph composer” to be selected.
Check that the designated stop character or GREP pattern is present.
Check for any nested style conflicts, resulting in two character styles applied simultaneously to a character or word.
Check that center-aligned text does not also include a first-line indent.
Check that tabs used to center text are set to the mathematical center of the text box.
Links and Fonts
Text Flow and Pasteboard
All text boxes should be linked except tables, sidebars, and figure captions.
The pasteboard should be clear by the time a file is considered final.
Soft Returns and Paragraph Breaks
There should be no empty paragraphs, and spacing should not be added through the use of soft or hard returns.
Digital Hub and Sublime Text Checks
Export XML from InDesign to perform text checks. Convert the exported .xml file to ePub 3 in the Digital Hub. This will produce .sam, .scml, and .epub files.
Confirm that all characters use unique Unicode entities.
Confirm that all alerts/warnings will be addressed or do not apply to the current stage of the project.
Run Check 1: Text Patterns and Check 2: Titles, Phrases, Alt Text, and Indexes on the .scml file.
Note: Some searches will result in false positives.
Note: Errors may be discovered through Hub stats, conversion alerts, and reviews in Kindle Previewer and Ace by DAISY.
If Kindle Previewer’s Run Quality Checks tool indicates any dead URLs, have they been noted or addressed per the project specification?
Design
A design created in the WFDW results in a functional template that can be unique to a single title or the basis for future publications. Consult the Design QC Checklist to confirm that both the aesthetic and functional needs of the publication are being met.
Additionally, the creation of a design may reveal errors or inconsistencies in the source material to be addressed through editorial actions.
Approach the creation of a design in a similar manner to the typesetting procedure, whether starting with a brand new InDesign file or modifying an existing template. Import InDesign Tagged Text, define styles, and set up parent pages, taking all relevant factors into consideration.
Note: Consider modern design standards, accessibility, and reader comprehension when choosing elements for inclusion. The use of tables and dropcaps, for example, can hinder the reader rather than supporting comprehension. Similarly, using ragged right text rather than justifying paragraphs support the reading experience.
Design Prerequisites
Designs should address the needs of the full book, including elements that have not yet been created, such as indexes. Considerations include, but are not limited to, the following:
- Output requirements (e.g., trim size, signature size, print output settings)
- Source and reference materials
- Image requirements (size, placement, color vs. grayscale)
- Missing or TK materials
- Representative text showing all elements (e.g., epigraphs, blockquotes, heads, notes, special characters, and character styles)
Fonts
Use Adobe and OpenType fonts. (Type 1 fonts are not supported by Adobe.)
Select fonts by considering factors including readibility, tone, and the support of special characters used in the book.
Ebook and Multipurpose Considerations
Choose design elements that do not interfere with or contradict the needs of other versions, such as an ePub. Without sacrificing aesthetics, designs created in the WFDW should result in typeset files that can export to XML and use standard procedures to process ScML and facilitate ePub creation.
Cover and Jacket Designs
Cover and jacket designs do not require the content to be functional, as they can be far removed from a book’s structure. However, titles, advanced praise quotes, book descriptions, and author biographies should be checked for text errors and consistency with the interior copy.
Design covers and jackets to meet the aesthetic needs of the book while meeting the necessary printer output requirements and measurements.
Requirements to confirm and review include the following:
- Text elements
- Measurements
- Positions
- Color
- Barcodes
- Consistency with interior
Design QC Checklist
General Checks
ScML
Specifications and Output Requirements
Examples: using extreme baseline shift instead of spacing settings; using overrides instead of dedicated styles
Source Materials
Image Requirements
Check image size/resolution, rotation, location, color settings, and cropping.
Missing Materials
Representative Text
Examples: the longest title or head; the most complex poetry; the most complex equation
Have exceptions, strategies, and source errors been noted for future reference?
InDesign/PDF Checks
Reference Files and Author Intent
File Measurements
Check the trim size, internal measurements, and bleed.
Paragraph Styles
Examples: copyright, praise page, index
Aspects include: font, size and leading, alignment, keep options, hyphenation, indents, spacing, justification, color, language and text direction, OpenType features
Spacing
Character Styles
WFDW Typesetting Conventions
Aesthetics
Aesthetic judgments can be based on author instructions, publisher guidelines, the needs of the publication, and other factors. As part of the vetting process and design preparation, the preferences and requirements of the appropriate people and institutions should be established as much as possible.
Font Choice
Content Arrangement and Ornamental Elements
Export Considerations
Check for text on a curved line or path.
Check for text placed as images.
Check for text or figures created as line art within InDesign.
Check for instances of multiple overlaying text boxes used to create a visual effect.
Parent Pages
Running Heads and Text Variables
Examples: Alt styles; text that mixes character styles
Live Content
Object Styles
If text wrap is being used, does this interfere with the vertical alignment of body text?
Example: gradients created in InDesign do not transfer to ebook.
InDesign’s Deeper Features
Features include: nested styles, GREP styles, automated footnotes, clip libraries
Cast-Off and Page Length Requirements
Tables
Accessibility and Future Uses
Aspects for web PDFs include: reading order, alternate text, and metadata
Document Preferences
Cover/Jacket Checks
Cover and jacket designs will follow most of the InDesign/PDF checks with an increased focus on strictly aesthetic considerations (at the proper measurements). Following proper ScML usage to create a functional template is often not required.
Images
Are the images placed at the appropriate size?
Have images been obtained from royalty-free resources (e.g., Shutterstock, Depositphotos)?
Do the images used fit into the project’s budget?
Jackets
Consistency with Interior
Aspects include: title, author name, display font, term usage
Spine Width
If the spine width is not yet established, how will this number be obtained?
Barcode
If unavailable, has a placeholder box been used to indicate its placement?
If a barcode has not been provided, how will it be obtained?
Bible Typesetting
Bible IDTT
InDesign Tagged Text (IDTT) often contains distinctions in the style names that are not compliant with ScML or standard typesetting style naming conventions. Examples include styles to handle the alignment of chapter or verse numbers embedded in paragraphs such as pf-h1 or sl-v1. The styles should only be used in projects generated from an established database, with no expectations that the bible content will be exported from the typeset.
Bible Typography Standards
- Bibles, particularly when set in two columns, often require greater leniency for stacks, widows, and orphans.
- Do not allow “Jesus” to hyphenate.
- Consult publisher- or project-specific guidelines for hyphenation rules in particular Bible versions. See also Scribe’s Bible Hyphenation list.
Deduping
Deduping is the process of removing duplicate instances of footnotes in a Bible typeset.
Deduping Manually Placed Footnotes
- Match the first sigla. Change the letter of the second fnref in the text to match that of the first.
- Renumber/reletter subsequent sigla. Renumber/reletter all of the note references that follow the first changed fnref on the page.
- Adjust the verse number in the footnote. Cut the verse number from the beginning of the second footnote and paste it after the verse number for the first note. Separate the verse numbers with a comma with no space.
- Delete the second note in the footnotes box.
- Renumber/reletter the remaining notes.
Deduping Automated Footnotes
- Adjust the verse number in the footnote. Cut the verse number from the beginning of the second footnote and paste it after the verse number for the first note. Separate the verse numbers with a comma with no space.
- Match the first sigla. Remove the auto-generated fnref for the second footnote from the text. Replace it with the literal character that matches the sigla for the first footnote.
Note: Removing the auto-generated fnref will also remove the footnote text and renumber subsequent footnotes in the file.