Shakespeare Dictionary Romeo And Juliet

Getting Past the Language Barrier in Romeo and Juliet

Shakespeare's verse is dense and deliberately archaic. Most readers hit a wall somewhere in Act 2, Scene 2 when Romeo starts speaking in iambic pentameter that feels more like a riddle than romance. A focused reference tool cuts through that friction. The Shakespeare Dictionary Romeo And Juliet concept exists because individual word meanings shifted enough between Early Modern English and now to make comprehension genuinely difficult without a companion guide. I ran into this problem myself last year while preparing a seminar on the play's rhetorical devices. I had twenty students all reading from the same Folger edition, but roughly half of them were stuck on line-by-line translation rather than engaging with the text. One student, Sarah, was literally stopping at every single line to look up words. By Act 3 she had burned through forty pages of dictionary entries and still couldn't parse the scene's structure. She was reading slower than a third-grade level book would demand. That's a classic trap with comprehensive dictionaries — they become a crutch that actually slows you down instead of helping. The workaround I used was to build a custom quick-reference deck. Instead of looking up every unfamiliar word, she only looked up the words that were blocking sentence-level comprehension. We identified roughly 150 key terms that covered maybe eighty percent of the barriers across the entire play. The rest were either archaic forms she could decode from context or proper nouns that didn't need translation at all. That reduced her lookup time from about three hours per scene down to roughly fifteen minutes.

Building a Shakespeare Dictionary Romeo And Juliet Reference

Start by pulling the actual text into a clean document. The MIT Shakespeare project provides free plain text versions with line numbers. Import that into a spreadsheet alongside a digitized Early Modern English dictionary like the OED or the Dictionary of the Historical Theme of the Language of Shakespeare. Cross-reference the two. Flag entries where a word appears fewer than five times in the entire play — those are low priority. Words appearing ten or more times, like "wherefore," "doth," "hath," "anon," and "ere," deserve full definitions with contextual examples from the play itself. I found that the most useful format was a three-column table: the word, its meaning in the specific Romeo and Juliet context, and one example line from the play. You don't need a full dictionary definition. Most students don't care about the etymology of "gall" when it appears in line 42 of Act 1. They need to know it means "bitterness" or "poison" in that moment. A tight contextual definition takes about ten seconds to read versus thirty seconds for a standard dictionary entry. Over a full scene, that difference compounds fast. Here is the part most people skip. You need to tag each entry with its part of speech. Shakespeare uses the same word as a noun, verb, and adjective frequently. "Love" is the simplest example. In Act 1, Scene 1, line 192, Romeo says "Love is a smoke made with the fume of sighs." Here it functions as a noun. Later in Act 2, Scene 1, line 171, Mercutio jokes about being "caught by love." Now it's functioning adjectivally. Without that distinction, a single dictionary entry will confuse more than it clarifies. I spent about four extra hours doing this tagging on my version and it cut misreadings down significantly during our discussion sessions.

What to Include and What to Leave Out

A working reference for this play should cover approximately 600 to 800 unique headwords depending on how granular you get. Anything above that and you're copying a full dictionary, which defeats the purpose. The bottleneck is not vocabulary size — it's the sheer number of obsolete conjugations and inversions that trip people up. "Goest thou" versus "goest thou not" versus "goest not thou" — these structural questions matter more than any single word definition. Your reference should note these patterns separately, ideally with a section on common syntactic inversions. Names and places also consume a surprising amount of lookup time. "Verona" and "Padua" show up repeatedly as social markers. Students who don't know what those cities represent end up missing whole layers of meaning. Brief geographic and cultural notes next to place names cost almost nothing to add and prevent a lot of confusion later. I included side notes for Montague versus Capulet as social standings too. The feud is not just family drama. It's class tension dressed as family drama, and that matters for scene analysis. There is a real limitation here that I should be blunt about. A word-level reference only gets you so far. Shakespeare's comedy often lives in double entendres and wordplay that a simple definition cannot capture. When Mercutio dies in Act 3, Scene 1, he says "Ask for me tomorrow and you shall find me a grave man." The joke is on "grave" meaning both serious and dead. A dictionary will give you both definitions but will not tell you which one is active in the moment. You need a commentary layer on top of any dictionary you build. This is where the Arden, Oxford, or Norton editions become necessary. They provide the scholarly apparatus that a standalone word list cannot replace.

If you are doing this for personal study rather than teaching, I recommend starting with the Free Shakespeare Dictionary database at shakespeare-online.com and cross-referencing with the MIT texts. That combination covers most needs for a single-person read-through. If you are preparing a classroom curriculum, invest the time in the spreadsheet approach I described. The upfront investment of about six hours pays off immediately after the first class discussion.