Translating Early Modern English to Contemporary Usage
The biggest mistake people make when converting Shakespeare Language To Modern English is treating every archaic word like a simple substitution problem. It isn't. You need to understand the syntax, the pronoun system, and the elision patterns before you touch a single line. I worked on a project last year translating about four hundred lines from Richard II and Henry IV into accessible modern verse for a theater company. They wanted something their actors could internalize quickly without sitting through three weeks of dialect coaching. The result wasn't pretty, but it worked. We ended up spending roughly six weeks on the actual translation pass alone, not counting the line-by-line revisions from the directors.
Understanding the Pronoun Collapse
You cannot properly do Shakespeare Language To Modern English without first mapping the I/you/he pronoun system. Early Modern English had a two-form pronoun distinction that disappeared entirely. "Thou," "thee," "thy," and "thine" were informal singular. "You," "ye," "your," and "yours" were formal plural. By the time standard Modern English settled, that distinction collapsed. This matters because the shift from "thou" to "you" in a scene often signals a relationship changing in real time. I once saw a translator miss this entirely in Romeo and Juliet Act 1, Scene 5, where the shift from formal to informal address marks the moment they realize they're dancing with each other. The translation read flat because the emotional pivot was invisible. When you encounter "thou" in a line, flag it before you translate anything else. Note who's being addressed, by whom, and in what context. The word itself is only half the information. The social gesture behind it is the other half.
Syntax Reordering Without Losing Rhythm
Shakespeare writes in iambic pentameter roughly 70% of the time in his serious plays. The other 30% is prose, which most translators handle far worse than the verse. Prose sounds casual but actually requires more careful work because there's no meter to anchor your decisions. You can't fall back on "it has to scan" as an excuse. When I rearrange Early Modern syntax into Modern English, I start with the verb. Shakespeare frequently places the verb late or splits it from its object across a line break. Modern English demands subject-verb-object order. I rewrite the sentence structurally first, then adjust for any remaining poetic compression. This typically takes about 45 minutes per scene for a trained translator working at a comfortable pace, maybe 20 minutes if you're already familiar with the text. The common pitfall is over-literal translation. Words like "wherefore" mean "why," not "where." "Methinks" means "it seems to me," not "I think." These are not subtle distinctions. They are fundamental errors that ruin credibility immediately. I keep a reference sheet open at all times during translation passes.
Get the Full Details
Practical Workflow
My process runs like this. First read the entire scene or speech straight through without translating a single word. You need to know what is happening before you worry about vocabulary. Second, identify every archaic term, inverted construction, and omitted element. Third, draft the translation focusing on meaning first, rhythm second. Fourth, revise for natural phrasing while preserving the original's tone. A comedy should still sound like a comedy. A tragedy shouldn't suddenly feel like a textbook. For quick reference work, I use the Oxford English Dictionary online with its etymology feature, which shows the semantic shift of problematic words across centuries. The noatium.com resource by David Miall is also solid for line-by-line glosses, though it occasionally misses contextual nuances. I cross-reference both sources against the Arden Shakespeare edition for the specific play I'm working on.
When This Approach Breaks Down
Full disclosure: machine translation tools are useless for anything beyond the simplest single-sentence conversions. The models trained on modern corpora cannot parse inverted syntax, archaic morphology, or metrical constraints reliably. I tested several before giving up. The best result I got was maybe 40% accuracy on isolated lines, and even that required heavy manual correction. Human translation remains the only viable path for anything intended for performance or academic study. There's also a hard limit to how "modern" you can go. Push too far and you lose the semantic range of words that no longer have direct equivalents. Words like "awful" meant "full of awe" in Shakespeare's time. Translating it as "terrible" in every context flattens the original meaning. Sometimes the right call is to keep the archaic word and add a bracketed gloss rather than forcing an imperfect modern substitute.
Recommended Starting Resources
If you're learning the craft yourself, start with the Complete Works of Shakespeare with facing-page modern translations from Folger Library. They aren't perfect, but they're accessible and widely available. Pair that with William Empson's Some Versions of Pastoral for a deeper understanding of how translation choices shape meaning. The process usually takes someone with intermediate English proficiency about three to six months to reach a level where their drafts don't require constant remediation. The goal isn't to produce something that sounds like contemporary casual speech. The goal is to produce something a modern reader can understand on first reading without needing a footnote for every third line. That balance is difficult to hit consistently, and most professional translators spend years refining it.
