Encode Hungwords in Semi-Diplomatic Transcriptions

Introduction

When a semantic line is too long for the compositorial line, the compositor will insert the final word(s) on the line above or below, usually inserting an opening parenthesis before the word(s).
Collectively, these words are known as hungwords. Words that are set above the semantic line to which they belong are known as turnovers:

                           Scan of an early modern book. Modernized version of relevant section reads: K. May we with right and conscience make this claim? Claim? is prefaced by ( and is typed at the end of the line above, over make this.
Words that are set below the semantic line to which they belong are known as turnunders:

                           Scan of an early modern book. Modernized version of relevant section reads: Would suck her eggs, playing the mouse in absence of the cat: Cat: is prefaced by ( and is typed at the end of the line below, underneath of the.

Practice: Encode Hungwords

When you are transcribing your semi-diplomatic transcription, type the hungword in the semantic line to which it belongs. Wrap all hungwords in the <seg> element. To differentiate between turnovers and turnunders, use the @type attribute with a value of either "turnover" or "turnunder" as appropriate.
Example of a turnover:
<body>
  <sp>
    <speaker>K.</speaker>
    <ab>May we with right & conscience make this<seg type="turnover">(claime?</seg>
    </ab>
  </sp>
</body>
Example of a turnunder:
<body>
  <sp>
    <speaker>Lord.</speaker>
    <ab><!-- … -->
      <lb/>Would suck her egs, playing the mouse in absence of the<seg type="turnunder">(cat:</seg>
      <!-- … -->
    </ab>
  </sp>
</body>
You will add styling to push the hungwords above or below the line as needed.

Special Case: Encode Hungwords on Empty Lines

Some hungwords appear on an otherwise empty line:

                           Scan of an early modern book. Modernized version of relevant section reads: Bell. So poke my ruff now, my gown my gown, have I my fall?. I my fall is prefaced by ( and is typed at the end of the line below, underneath gown, have
If you come across this scenario, encode the hungword using the <space> element as usual. Encode the white space as vertical white space. See Practice: Encode Vertical White Space.
For example:
<sp xml:id="emd1HW_Q1_sp329">
  <speaker>Bell.</speaker>
  <ab> So Poke my ruffe now, my gowne, my gown, haue <seg type="turnunder">(I my fall?</seg>
    <space dim="vertical" unit="line" quantity="1"/>
  </ab>
</sp>

Practice: Style Hungwords

You must add inline styling using the @style attribute in order to make hungwords appear in the space that they do in your copyext.
You will add two properties on the @style attribute for hungwords. The first is "position:", which you will give a value of "absolute;". The second is "margin:". The value for "margin" has two components:
The vertical margin, starting from the top of the element.
The horizontal margin, starting from the left of the element.
The two components should be seperated by a space.
For turnunders, give the "margin" property a value of "1.8rem". This will move the hungword one line below the one that it semantically belongs to.
For turnovers, give the "margin" property a value of "-1.8rem". This will move the hungword one line above the one that it semantically belongs to.
You will need to experiment with the horizontal component of the "margin" property. To move the hungword to the left (which is typically what you will want to do), use a negative number followed by the unit "rem". For information on how to test and tweak the values for your horizontal margin, see Practice: Tweak CSS Values.
Example of a styled turnunder:
<seg type="turnunder" style="position: absolute; margin: 1.8rem -5rem;">(ciphered.</seg>
Example of a styled turnover:
<seg type="turnover" style="position: absolute; margin: -1.8rem -5.1rem;">(pre<g ref="g:longS">s</g>ently.</seg>

Prosopography

Janelle Jenstad

Janelle Jenstad is a Professor of English at the University of Victoria, Director of The Map of Early Modern London, and Director of Linked Early Modern Drama Online. With Jennifer Roberts-Smith and Mark Beatrice Kaethler, she co-edited Shakespeare’s Language in Digital Media: Old Words, New Tools (Routledge). She has edited John Stow’s A Survey of London (1598 text) for MoEML and is currently editing The Merchant of Venice (with Stephen Wittek) and Heywood’s 2 If You Know Not Me You Know Nobody for DRE. Her articles have appeared in Digital Humanities Quarterly, Elizabethan Theatre, Early Modern Literary Studies, Shakespeare Bulletin, Renaissance and Reformation, and The Journal of Medieval and Early Modern Studies. She contributed chapters to Approaches to Teaching Othello (MLA); Teaching Early Modern Literature from the Archives (MLA); Institutional Culture in Early Modern England (Brill); Shakespeare, Language, and the Stage (Arden); Performing Maternity in Early Modern England (Ashgate); New Directions in the Geohumanities (Routledge); Early Modern Studies and the Digital Turn (Iter); Placing Names: Enriching and Integrating Gazetteers (Indiana); Making Things and Drawing Boundaries (Minnesota); Rethinking Shakespeare Source Study: Audiences, Authors, and Digital Technologies (Routledge); and Civic Performance: Pageantry and Entertainments in Early Modern London (Routledge). For more details, see janellejenstad.com.

Joey Takeda

Joey Takeda is LEMDO’s Consulting Programmer and Designer, a role he assumed in 2020 after three years as the Lead Developer on LEMDO.

Mahayla Galliford

Project manager, 2025-present; research assistant, 2021-present. Mahayla Galliford (she/her) graduated with a BA (Hons with distinction) from the University of Victoria in 2024. Mahayla’s undergraduate research explored early modern stage directions and civic water pageantry. Mahayla continues her studies through UVic’s English MA program and her SSHRC-funded thesis project focuses on editing and encoding girls’ manuscripts, specifically Lady Rachel Fane’s dramatic entertainments, in collaboration with LEMDO.

Martin Holmes

Martin Holmes has worked as a developer in the UVic’s Humanities Computing and Media Centre for over two decades, and has been involved with dozens of Digital Humanities projects. He has served on the TEI Technical Council and as Managing Editor of the Journal of the TEI. He took over from Joey Takeda as lead developer on LEMDO in 2020. He is a collaborator on the SSHRC Partnership Grant led by Janelle Jenstad.

Navarra Houldin

Training and Documentation Lead 2025–present. LEMDO project manager 2022–2025. Textual remediator 2021–present. Navarra Houldin (they/them) completed their BA with a major in history and minor in Spanish at the University of Victoria in 2022. Their primary research was on gender and sexuality in early modern Europe and Latin America. They are continuing their education through an MA program in Gender and Social Justice Studies at the University of Alberta where they will specialize in Digital Humanities.

Rylyn Christensen

Rylyn Christensen is an English major at the University of Victoria.

Tracey El Hajj

Junior Programmer 2019–2020. Research Associate 2020–2021. Tracey received her PhD from the Department of English at the University of Victoria in the field of Science and Technology Studies. Her research focuses on the algorhythmics of networked communications. She was a 2019–2020 President’s Fellow in Research-Enriched Teaching at UVic, where she taught an advanced course on Artificial Intelligence and Everyday Life. Tracey was also a member of the Map of Early Modern London team, between 2018 and 2021. Between 2020 and 2021, she was a fellow in residence at the Praxis Studio for Comparative Media Studies, where she investigated the relationships between artificial intelligence, creativity, health, and justice. As of July 2021, Tracey has moved into the alt-ac world for a term position, while also teaching in the English Department at the University of Victoria.

Orgography

LEMDO Team (LEMD1)

The LEMDO Team is based at the University of Victoria and normally comprises the project director, the lead developer, project manager, junior developers(s), remediators, encoders, and remediating editors.

Metadata