Translating Ancient Epics: What Simon Armitage's Gilgamesh Teaches Student Writers
Translating ancient epics raises a practical problem before any sentence can shine: how will readers recognise unfamiliar people, places, and named creatures? The Guardian review of Simon Armitage's Gilgamesh names Gilgamesh, Enkidu, Humbaba, Ishtar, the Cedar Forest, and the Bull of Heaven. Those references give us material for an original student workshop on names and their referents, rather than evidence about Armitage's translation decisions. Our proposed method is to build a name register, connect descriptive labels to the right entry, prepare restrained glossary notes, and document the naming conventions of the version you use.
Build a Register of Names and Referents
Our suggestion is to begin with a register that separates a printed name from the person, place, or creature it identifies. In the supplied review, Gilgamesh is the king of Uruk, Enkidu is described as a wild man, and Humbaba is identified as guardian of the Cedar Forest. Ishtar is named as a goddess, while the Bull of Heaven is presented as a winged creature. These descriptions are limited to what the review supplies; they do not establish the spelling or meaning of names in an ancient language. Give each entry a simple reference code, such as P1 for a person or L1 for a location, without replacing its printed name in your eventual prose.
Our exercise: copy six names exactly as they appear in a short source passage and create four fields for each: printed form, type of referent, source location, and information explicitly supplied there. Include the name of the published translation if that is your source. Where a field cannot be completed, leave it open. Do not fill a missing description from memory. Then identify a place where two entries are related without being interchangeable, such as a guardian and the place guarded. Give them separate reference codes. Your completed register should let you explain what each name identifies and where that identification came from, without offering a speculative meaning or pronunciation for the name itself.
Connect Titles and Descriptions to the Right Entry
A name register also needs a place for descriptive labels. The supplied review identifies Gilgamesh as king of Uruk and describes Enkidu as a wild man. In our workshop, those descriptions can be recorded beside the relevant name without being mistaken for additional characters. This is a reference-handling exercise, not an argument that every use of a title has one fixed meaning across an entire epic. Our suggestion is to draw a small label box beside each register entry and include only labels whose connection you can establish in the chosen passage. If a description could refer to more than one figure, mark that uncertainty rather than assigning it automatically.
Our exercise: take a paragraph from your chosen published version and mark proper names with one colour and descriptive labels with another. Draw a line from each label to an entry only when the wording makes the reference clear. For example, a phrase such as 'the king' needs a local basis before you connect it to a particular named figure. Record that basis in a brief note. Keep unassigned labels in their own box. The resulting sheet should distinguish a name, a description, and your decision about their relationship. It should not turn a convenient classroom label into an assertion about the original language, the author's intention, or every appearance of that figure elsewhere in the work.
Write Glossary Notes Without Inventing Name Meanings
Our suggestion is to make a short glossary from the completed register. Each entry needs only the printed name, a supported identification, and a pointer to the source passage. For this workshop, a note on Humbaba could identify him as guardian of the Cedar Forest because the review supplies that description. It should not add an etymology, an ancient pronunciation, or a claim about how Armitage selected the English spelling. A useful student glossary can be modest. Its job here is to keep references available to a reader who encounters unfamiliar names, while making the limits of the supporting material visible. Leave a question open when the available source does not answer it.
Our exercise: write three glossary entries of twenty to thirty words each, excluding the source reference. Underline the words that identify the referent and circle anything that claims to explain the name's origin or meaning. Find a source for every circled claim or remove it. Next, check whether two entries define each other without providing an independent identification. A note that says only 'Humbaba: associated with the Cedar Forest' leaves the relationship unclear; a source-supported description of his role is more informative. Keep the glossary beside the passage rather than expanding it into a general account of mythology. The finished notes should tell readers what they need for this passage and make no promise to explain the entire tradition.
Document the Naming Conventions of Your Chosen Version
Our suggestion for the final part of the workshop is a naming-conventions sheet. Record the published version you consulted, the printed forms you copied, and where you use each form in your own retelling. If you consult a second version, start a separate column and enter a spelling only after checking that copy. Do not invent a variant to make the comparison look complete. Similar-looking names do not by themselves establish that two references identify the same figure. Keep an unresolved match unresolved until your sources support it. This gives students a practical way to document a retelling based on particular reading, without presenting its names as a newly verified translation from an ancient language.
Our exercise: prepare a one-page companion sheet containing your six-entry register, three concise glossary notes, and the version reference. Choose one place in your retelling where a descriptive label introduces a name and show how that connection appears on the sheet. Keep any invented nickname in a separate, clearly marked adaptation field, rather than mixing it with forms copied from the source. If you work across two languages, record both consulted versions and distinguish your own choices from their printed forms. Finish by describing the activity accurately: a reference workshop for a retelling based on named reading. The resulting sheet makes unfamiliar names manageable while leaving unsupported linguistic claims and invented background outside the source record.
Sources
- Gilgamesh by Simon Armitage review – an ancient epic is brilliantly translated for our times — www.theguardian.com,