Coding and Typemarking

We ask copy editors to apply type coding tags to key text elements to serve as editorial guides for typesetting, and to call the typesetter’s attention to special text elements such as sidebars and block quotes. The following instructions will guide you in coding New Harbinger manuscripts. 

We recognize that coding is a complex task. Reach out to your supervising editor anytime with any questions you may have about it.

You may also consult the following coded manuscripts to see these instructions applied: 

• The Body-Based Obsessions Workbook (8x10, workbook)

• EMDR for Anger Management (6x9, trade)

General Guidance

1. Insert a type code inside <angle brackets> immediately preceding these key text elements:

Dedication <ded>

Table of Contents <toc>

Part Title <pt>

Part Number <pn>

Part Subtitle <ps>

Chapter Title <ct>

Chapter Number <cn>

Chapter Subtitle <cs>

A-Head <ah>

B-Head <bh>

C-Head <ch>

D-Head (run in head) <dh>

For these elements, there is no need to insert a closing code (i.e., a code that marks the end of a particular element), or to code the body text that follows the heads.

2. For the following text elements, insert coding instructions inside angle brackets at the beginning and end of the section, like this:

<start unnumbered list>sidebars

dialogues

epigraphs

exercises

blockquotes

lists (Specify type: numbered, unnumbered, bulleted, checklist, or sublist, meaning a list within a list.)

boxes

pull quotes (For guided journals and similar small-format books; we discourage pull quotes in trade books and workbooks.)

sidebars (For 7x10 and larger books. Code sidebar text in smaller-format books as a box.)

stories<end unnumbered list>

Some additional notes regarding coding of these elements:

• Clearly indicate both beginning and ending of all exercises, text boxes, sidebars, stories, and lists.

• Please ensure your coding is consistent across the document. For instance, do not alternate between “start” and “begin” in your opening codes. Choose one and employ it throughout.

• It’s up to you whether to spell out elements in your codes (ex., <start unnumbered list> <end unnumbered list>) or abbreviate (<ul> </ul>). Some editors prefer the latter. Whichever you choose, though, make sure it’s consistent across the document.

• Note list titles should be coded, specifically as <list head> or <lh>. Also code exercise titles (<exercise head> or <exh>) and story titles (<story head> or <sth>) in this way.

• Do be sure to code heads within exercises and stories, too, when you’re coding multi-level exercises (exah, exbh, etc). Finally, please double-check that all exercises have <end exercise> codes. Otherwise, there’s no way for our Production team to tell when an exercise ends and general text resumes.

• Tables do not need to be coded, since we can work with the ones created in Word. But if a given table includes a table title, code it as a table head: <th> or <table head>.

• Any worksheet heads (e.g., in online-only free tools, or any worksheets in the running text of a book that the author would like to have stand alone, on their own pages) should be coded <wsh>. 

• Note that occasionally, codes will be nested, as with the list head code here: 

<begin bulleted list><list head>Title of List

If you ever have questions about precisely how a given set of codes should nest, contact the supervising editor.

• One fine point regarding D-heads: Note <dh> is a character code. It applies only to text in general/paragraph form. As such, <dh> should not be used in lists (whether bulleted, numbered, or unnumbered). If you want to highlight the lead-in to a particular bullet or numbered list item as such, just set that text bold.

Finally, there’s no need to code figures, created in Word, that are embedded in the text—but if you see figure captions, code them as <figcap>.

3. If you are inserting an instruction to Production in the manuscript file (for example, to let the typesetter know where a figure should go), enclose it in [[double square brackets]]: ex., [[insert Figure 3 here]] 

Note: If you’re inserting callouts for blank lines, please be sure this instruction is consistent. I.e., do not alternate between [[insert X lines]] and [[insert X blank lines]]. Please use the former styling, and make sure it's done consistently throughout your coding.

4. Please keep a running list of the codes you've used in your style sheet for the project for Production's reference in typesetting. If there’s anything you can’t figure out how to code, make a note of it and tell us what/where it is when you return the edited ms to us.

Coding a Workbook

Here are some points of guidance specific to workbooks and the complex fill-in sections they may contain. 

• For fill-ins, please specify how many lines are needed for each, using double square brackets: “[[insert 3 lines]],” etc.

• Please be sure you’re using double square brackets. Do not use angle brackets (<>), single square brackets ([]), or any other type of formatting for fill-ins.

• Please use numerals in these callouts. Do not spell out numbers. I.e., “[[insert 3 lines]],” not “[[insert three lines]].”

• Finally, please be consistent with these callouts. I.e., do not alternate between [[insert 2 lines]] and [[insert 2 blank lines]]. Generally, "blank" goes without saying, so there's no need to specify it. 

So, putting all the above pieces of guidance together: 

❌ What would you tell her if she asked? _______________________

____________________________________________________________________

❌ What would you tell her if she asked? [[insert two lines]]

❌ What would you tell her if she asked? [[insert 2 blank lines]]

✅ What would you tell her if she asked? [[insert 2 lines]]

• If an exercise requires a short blank line, rather than one that runs to the end of the available space, you may indicate that in your instruction: i.e., "[[insert 1 short blank]]"

• If the lines need to appear in any sort of configuration, you can use double-bracketed notes to Production to specify this: ex.,

[[Prod.: Please insert 3 rows of short blank lines, as in the below example:

__________ __________ ]]

Instant Help Workbooks

If you are coding an Instant Help workbook for teens or kids, here are some additional pieces of guidance:

• Headings within activities should be coded as a-heads. Activity titles can be coded with chapter number and chapter title codes (<cn>, <ct>).

• Occasionally, authors will begin activities with a sort of “topline”—one or two sentences that boil down the key insight of the activity. These, you can code as <lo> so that Production knows the lines are meant to stand alone.

• If the lines need to appear in any sort of configuration, again, use double-bracketed notes to Production to specify this: ex.,

[[Prod. Please insert 3 rows of short blank lines, as in the below example:

__________ __________ ]]

• Also use double-bracketed notes to Production to specify any special art or design needs, particularly for activity books.