Appearance
To expand common Latin abbreviations reliably, identify each sign's class first (suspension, contraction, special sign, or superscript), expand it to the grammatically correct Latin form for its context, and record a single documented policy for how supplied letters are marked. The biggest quality risk is inconsistency, so the working goal is a defensible, repeatable system rather than ad-hoc guesses, with Cappelli's lexicon as the arbiter for anything unfamiliar.
Why a documented policy matters more than memory
Across a long document or a multi-editor project, the same sign will appear hundreds of times. If you expand it from memory you will drift, and a reviewer cannot audit your choices. A written policy and a project glossary make every expansion checkable and let collaborators converge. This is the difference between a transcription that survives peer review and one that quietly contradicts itself.
What are the four classes of abbreviation?
Every Latin abbreviation falls into one of four families, and the class tells you how to expand it:
| Class | Mechanism | Example | Expansion |
|---|---|---|---|
| Suspension | end cut off | dns | dominus |
| Contraction | middle omitted, macron over | dñs, oīa | dominus, omnia |
| Special sign | dedicated mark | p̄, ꝓ, ꝯ | per/par, pro, con/com |
| Superscript | raised letter signals ending | q̔, vowel above | qui/quod etc. |
The p family is worth memorising because it is everywhere in charters and legal text: p with a crossed descender is per or par, p with a curl through the descender is pro, and a p with a superscript is pre.
How do you expand the most frequent signs?
A core kit covers the bulk of medieval Latin documents. Keep this within reach:
text
Nomina sacra & high-frequency contractions
dñs / dñi = dominus / domini
ihs / xps = Iesus / Christus
sēs / sca = sanctus / sancta
oīa = omnia
nr / nostr̄ = noster (decline to context: nostri, nostrum...)
ē / ē(st) = est
& / ⁊ = et (ampersand / tironian et)
9 (open) = con- or com- (initial) / -us (final)Note the position-dependent sign: the open-9 graph means con/com at the start of a word but -us at the end. Position changes meaning, so never expand a sign in isolation.
How do you decide between two valid expansions?
The deciding factor is grammar, not the lookup table. A macron-bearing dñm is dominum in the accusative but dñs is dominus in the nominative; the surrounding syntax dictates the case. Work through it:
- Identify the sign's class and its base expansion.
- Determine the grammatical role of the word in the sentence.
- Supply the case, number and tense ending that the Latin requires.
- Sanity-check against a parallel passage or a known formula.
When two expansions remain genuinely possible, record both and mark the reading as uncertain rather than forcing a choice.
What is a practical quality checklist?
Run every transcription against a fixed checklist before sign-off:
text
Abbreviation QA checklist
[ ] Editorial policy stated (italics? brackets? silent?)
[ ] Project glossary updated with every new sign
[ ] Position-sensitive signs (9, p-family) checked for context
[ ] Expansions grammatically agree with surrounding Latin
[ ] Uncertain readings flagged, not silently resolved
[ ] Nomina sacra expanded per house style, not literally
[ ] Cappelli / Abbreviationes consulted for any unknown sign
[ ] Spot-check 10% of expansions against a second readerA two-reader spot-check of even ten percent catches systematic drift early and costs little.
How should this fit into a digital edition?
Best practice separates the transcription layer from the expansion layer so both stay auditable. In TEI XML you can keep the abbreviated form and the expansion together using abbr and expan inside a choice element, which lets you render either a diplomatic or a normalised view from one source. This keeps the original visible for verification while delivering a readable text, and it means HTR-assisted projects can store "as written" output and expand in a documented, reversible step.
Key Takeaways
- Classify each sign first (suspension, contraction, special sign, superscript); the class governs the expansion.
- Expand to the grammatically correct Latin form for the context, not a fixed lookup value.
- Position changes meaning: the open-9 sign is
con/cominitially but-usfinally. - Write down one editorial policy and apply it consistently across the whole project.
- Maintain a living project glossary and consult Cappelli or Abbreviationes for unknown signs.
- In TEI, use
choicewithabbrandexpanto keep diplomatic and normalised views from one source. - Run a checklist and a two-reader spot-check to catch systematic drift.
Frequently Asked Questions
What are the main classes of Latin abbreviation?
The standard scheme follows Cappelli: suspension (the end is cut off), contraction (the middle is omitted with a macron), abbreviation by special signs (per, pro, con marks), and abbreviation by superscript letters. Knowing the class tells you how to expand it.
Should expanded letters be marked in the transcription?
In a diplomatic or semi-diplomatic edition, yes: convention is to render supplied letters in italics or within round brackets. In a normalised reading text you expand silently. State your choice in the editorial note.
What is the single most useful reference?
Adriano Cappelli's "Dizionario di abbreviature latine ed italiane" (the "Lexicon Abbreviaturarum") is the standard. A searchable online version, Ad fontes and the Abbreviationes database, lets you look up unfamiliar signs quickly.
How do I expand a macron correctly?
A macron over a vowel usually signals an omitted m or n; over or through a consonant it can mark a contraction. Context and the word's expected Latin form decide between, for example, "comon" to "commun" versus "co(n)" forms.
Do regional or period conventions change expansions?
Yes. The same sign can expand differently in insular, continental, legal and humanist contexts, and case endings shift the expansion. Always expand to the grammatically correct form for the surrounding Latin, not a fixed lookup.
Can HTR models expand abbreviations automatically?
Transkribus and similar tools can be trained to output expansions, but accuracy depends on the training ground truth. Many projects transcribe abbreviations as written and expand in a separate, documented editorial layer for auditability.