Appendix 4. Legacy Markup
This chapter of our documentation is still in beta. We welcome feedback, corrections,
and questions while we finalize the page in our 2024–2025 work cycle.
¶ IML Conversion Table
¶ Context
¶ IML to TEI Typographical Conversion
| IML Typographical | TEI Element | TEI Attributes | Notes |
| [...] |
<supplied>
|
@reason with the appropriate value |
Square brackets correspond to supplied material |
| "..." |
<soCalled>
,
<mentioned>
,
<quote>
,
<title>
|
A propos
<title>
:
@level = a
|
The programmatic conversion will replace all quotations with
<q>
elements, and the remediator will make an informed decision during the remediation
process. |
¶ Tips for Editors Working in IML
This documentation contains tips for editors who are still working in IML (the old
ISE Markup Language). If you follow these tips, our programmatic conversions will
be better able to convert your IML tags to TEI tags, thus saving the person running
the conversions a good deal of time.
¶ General Tips
Below is a list of general tips for working in IML:
Do not add TEI tags to your IML. Our conversion processor is expecting valid IML,
not a hybrid of two markup languages.
Check your tag hierarchy carefully. Misplaced closing tags trip up our conversion.
Close all of your tags properly with </elementName>. Check that every closing tag
begins with a forward slash.
Do not use straight apostrophes or straight quotation marks except in the tags themselves.
It will be helpful if you can correct these before sending the files to LEMDO.
Check that quotations in the annotations and critical paratexts are properly wrapped
in beginning and ending quotation marks. Our processor is looking for opening and
closing quotation marks to wrap the quotation in the
<q>
element that LEMDO requires. It is very time consuming for the LEMDO team to look
up quoted material to see where the quotation begins and ends, and we do not have
the resources to do that kind of work for you.Edit the annotations and modern text file simultaneously. LEMDO uses string matching
in the process of adding anchors and pointers, but, unlike the ISE, we no longer rely
on string matching once the anchors and pointers are in place. If the lemma in the
annotation differs from the reading in the modern text, we have to compare the files
and try to figure out what the editor wants to annotate. Mistakes can occur if you
edit either the modern text or the annotation file without updating the other file
to match.
¶ Spaces
Do not use the <SPACE> element to add vertical space to your modern texts. LEMDO applies
generic styling to all modern texts, so there is no need to spend time adding tags
that will be deleted when we convert your IML to TEI and remediate it for publication
on the LEMDO platform.
You may continue to use the <SPACE> element in your semi-diplomatic texts to describe
vertical white space in the early modern manuscript or printed playbook.
If you are using the <SPACE> element to make something indent, there is probably a
semantic reason you are doing so. For example, it may be a letter read aloud within
a speech, or the couplet in a sonnet. In those cases, leave a note in your file and
we will encode the letter/couplet appropriately for you. You can wrap your note in
an xml comment like the one below:
<!-- LEMDO team: This passage of the speech is a letter. -->
¶ Collation
Do not use the @subst attribute. If you need to say more about the reading you have
adopted, add a
<note>
to your
<app>
element in the collation or a <note type="textual> in your annotation.¶ Use LEMDO Values in IML Annotations
IML annotations were organized into four levels: 1, 2, 3, and perf (for performance
notes, used mainly by QME editors). Editors working in IML were encouraged to think
about the levels according to the length of the annotation and whether or not it should
appear in a printed edition.
LEMDO annotations are based on an entirely different logic, that of the challenge
addressed by the annotation. Length is immaterial from LEMDO’s perspective; you will
want to consult with your anthology lead about your anthology’s requirements and standards.
Allowed LEMDO values are:
You will find definitions of these values in
gloss
commentary
textual
pedagogical
performance
lexical
Types of Annotations
You may begin using these values in your IML, or continue to use IML’s levels. LEMDO
prefers that you begin using our values because you will save our remediators a lot
of time (and that in turn saves money that is better spent on new features and remediating
other texts). In particular, we encourage you to start identifying notes about textual
matters as textual instead of Level 2 or Level 3 notes. Likewise, if you have extensive commentary notes
that quote from the OED or other dictionaries, please begin labelling these as lexical notes.
Our IML-to-TEI conversion process is expecting this encoding in your IML:
<LEVEL="[value]">. As of 2021-08-04, our conversion process will convert <LEVEL="[value]"> to TEI’s
<note>
element with a
@type attribute and value as follows:Value in IML <LEVEL="[value]">
|
Post-conversion value |
| 1, gloss | gloss |
| 2, 3, comm, commentary | commentary |
| perf, performance | performance |
| text, textual | textual |
| perf, performance | performance |
| lex, lexical | lexical |
| video | video (a temporary value assigned during conversion but not ultimately allowed in the LEMDO schema; LEMDO does not treat video links as annotations) |
Note that we have allowed for short forms of values in your IML. We know that many
of you are typing these values out in a word processed document and expect that you
may prefer to type a shorter form. We have also tried to anticipate typos and accidental
reversions to the numbers of the ISE’s levels.
¶ Substitutions and Notes
For
<LEVEL="1">, start using <LEVEL="gloss">.For
<LEVEL="2"> or <LEVEL="3">, start using <LEVEL="commentary">, <LEVEL="textual">, <LEVEL="lexical">, or <LEVEL="performance"> to describe the purpose of the note rather than its length.Note that performance is meant for discussions of specific performances. IML introduced this value for
QME’s Performance-As-Research. LEMDO extends QME’s practice to allow the use of performance to describe any specific production listed in your bibliography. General speculations
about early modern performance practices and observations about performance cruces
that have to be solved by directors (e.g., the timing of Feste’s exit when the letter
plot is fomenting in Twelfth Night) are commentary notes, not performance notes.
LEMDO’s pedagogical note type has no precedent in IML. LEMDO’s primary intention is to allow future scholars
and teachers to add pedagogical notes to an edition. If you wish to use it to point
out pedagogical opportunities or challenges in your own edition, consult with your
anthology lead.
Prosopography
Isabella Seales
Isabella Seales is a fourth year undergraduate completing her Bachelor of Arts in
English at the University of Victoria. She has a special interest in Renaissance and
Metaphysical Literature. She is assisting Dr. Jenstad with the MoEML Mayoral Shows
anthology as part of the Undergraduate Student Research Award program.
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 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.
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
Project manager 2022–present. Textual remediator 2021–present. Navarra Houldin (they/them)
completed their BA in History and Spanish at the University of Victoria in 2022. During
their degree, they worked as a teaching assistant with the University of Victoriaʼs
Department of Hispanic and Italian Studies. Their primary research was on gender and
sexuality in early modern Europe and Latin America.
Nicole Vatcher
Technical Documentation Writer, 2020–2022. Nicole Vatcher completed her BA (Hons.)
in English at the University of Victoria in 2021. Her primary research focus was womenʼs
writing in the modernist period.
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.
Metadata
| Authority title | Appendix 4. Legacy Markup |
| Type of text | Documentation |
| Short title | |
| Publisher | Linked Early Modern Drama |
| Series | |
| Source | |
| Editorial declaration | |
| Edition | |
| Encoding description | |
| Document status | prgGenerated |
| License/availability |