Skip to content
An independent guide to international theatreMany cultures. A shared stage.
The InternationalistsTHEATRE ACROSS BORDERS

A GUIDE TO THEATRE ACROSS BORDERS

Translation & Multilingual Theatre

What Should a Dramaturgical Pack Include for a Translated Play?

THE SHORT ANSWER

A dramaturgical pack for a translated play should do two jobs: give the production team the usual context, themes, production history and images, and make the translation itself legible. It should identify the source text and edition, the translator and translation history, key language and cultural choices, pronunciation and names, rights and credits, and audience-facing context. The pack is an internal working document, not a programme note, and should distinguish documented evidence from editorial interpretation.

At a glance Quick facts
Document type
Internal research dossier for a production team
Core double brief
Context for the play and visibility for the translation
Example teaching length
5–7 pages in one university dramaturgy brief
Key translation topics
Source edition, translator, cultural context, choices, pronunciation, rights
Useful comparator
Abbey Theatre resource pack for Brian Friel's Translations
Translator labour
Rendering a source-text world into a target language and culture

A dramaturgical pack for a translated play is a working dossier prepared for the director, cast, creative team and sometimes the producer or marketing team. It should answer two questions at once: what does this production need to know about the play, and what does it need to know about the translation? The first question belongs to production dramaturgy in general. The second is specific to work that crosses languages, and it is the part most often missing.

The pack is not the same as a programme note. It is an internal research document that gathers context, questions, images, glossaries and evidence in one place. A university dramaturgy brief describes the dramaturg as researching historical context, relaying it to actors and directors, pointing the team towards useful resources and images, reviewing production history, studying biographies, teaching themes, and supplying an interpretive lens; in that course the packet is set at 5–7 pages (Baruch College, Dramaturgy Packet). That length is a useful teaching constraint, not a universal rule. A professional pack may be a short quick-reference document with a larger digital appendix.

What production dramaturgy contributes

Dramaturgy handbooks distinguish institutional dramaturgy, production dramaturgy and portfolio work. Production dramaturgy is the research and communication that supports a particular rehearsal process and production (Magda Romanska, Dramaturgy Student Handbook). For a translated play, that support includes not only the play’s themes and historical world but the translator’s labour, the status of the text, and the choices that have made it speak in the target language.

Translation is not a neutral window. Kristi Good argues that each source text contains a world built from an author’s individual language and culture, and that a translator must render that world into a different language for a different culture while maintaining the essence of the source text. She also notes that translations make up nearly 70 per cent of the texts in her theatre history courses and urges readers to recognise the translator’s labour when selecting a script (Kristi Good, Best Practices for Selecting a Translated Script). A dramaturgical pack can make that labour visible to the rehearsal room.

Core sections of a translated-play pack

Most packs combine a synopsis, character list, historical and cultural context, themes, production history, images, glossary and further reading. The Abbey Theatre’s resource pack for Brian Friel’s Translations is a useful model for how such material can be organised: it includes a synopsis, characters and cast interviews, key themes, cultural context, literary genre, and a compare-and-contrast section (Abbey Theatre, Translations Resource Pack). It is important not to confuse the example: Translations is an original English-language play about language and translation, not itself a translated script. The pack shows how context and themes can be packaged, but a translated play needs additional sections.

SectionWhat to includeWhy it matters
Basic facts and synopsisTitle, author, source language, translator, version, date, setting, characters, plot.Gives a shared reference and clarifies which text is being rehearsed.
Source text and editionOriginal title, first publication or production, edition used, any cuts or adaptations.Prevents the team treating the translation as the original.
Translator and translation historyTranslator biography, other work, date of translation, publication or production history, revisions.Makes the translation a credited creative act.
Language and cultural contextSource culture, period, institutions, religious or political references, class and register, multilingualism.Supports acting choices and avoids flattening difference.
Translation choicesRecurring terms, idioms, forms of address, verse or prose, humour, taboo language, translator’s notes.Gives the room a vocabulary for discussing what the text is doing.
Pronunciation and namesPronunciation guide, stress, variants, place names, titles, forms of address.Supports vocal work and respectful address.
Production historyVerified prior productions, translations and adaptations, reception where documented.Shows the play’s life across languages without inventing a tradition.
Rights, credits and permissionsTranslation credit, rights holder, licence conditions, programme and marketing wording.Ensures legal and ethical attribution.
Further reading and sourcesEditions, interviews, reviews, archives, images with rights information.Allows the team to verify and go deeper.

Translation-specific sections in detail

1. Source text and edition

Start with the exact identity of the text: original title, source language, first publication or production where documented, and the edition used for rehearsal. If the production uses a published translation, record publisher, year and edition details. If it uses an unpublished translation, record the manuscript date and version. Distinguish translation from adaptation, version, literal translation and devised response. Good’s argument is useful here: selecting a translation means identifying a translator’s work, not simply choosing a language (Good). Avoid treating fidelity as a simple quality label; describe what the target text is doing.

2. Translator and translation history

Include the translator’s name, working languages, other translations, published notes or interviews where available, and whether the translation is new, previously published, previously produced or revised for this production. If several translations exist, a short comparison of one passage can be more useful than a general claim about which is better. Do not invent the translator’s intentions. Quote documented notes, correspondence or published commentary, and mark open questions clearly for the translator or director.

3. Language and cultural context

Research the source culture and language, but avoid treating a country or language as a single theatrical tradition. Identify the specific community, region, period, class, institution and language variety at stake. Explain references that may be opaque to the production team. For multilingual plays, identify which languages appear, who speaks them, and how the translation handles that multilingualism. Note register and forms of address, which often carry social meaning that a plot summary cannot convey.

4. Choices, variants and translator’s notes

Record recurring decisions: why a key word is rendered in one way, how idioms are handled, whether verse or song is rhymed, how dialect or slang is represented, and what may be lost or added. Short parallel examples can be useful, subject to permissions; otherwise paraphrase. The aim is not to police accuracy but to give the rehearsal room a shared vocabulary for discussing the text. The pack should separate what is documented by the translator from what is an editorial question or a director’s interpretation.

5. Names, pronunciation and onstage language

Provide a pronunciation guide, using IPA or simple respelling, with stress and known variants. Include place names, personal names and titles. If surtitles or projected text are used, record who prepares them, how they relate to the spoken text, and who checks accuracy and access. Surtitles are a translation layer in their own right and need credit and editorial care. Where accents or dialects are used, be specific about the place and community being represented rather than relying on generic labels.

6. Rights, permissions and credits

The pack should record the translator credit required by contract or programme, the rights holder, and any licence conditions relevant to the production. It should distinguish rights in the translation from rights in the underlying play. For cuts, adaptations or newly commissioned material, note what approvals are required. This is a practical and legal area, so the producer should verify details with the publisher, agent, translator or rights holder; the pack can record and flag the issue but cannot replace legal clearance.

7. Audience context and reception

A production-team pack can include audience-facing context: what a local audience may already know, what may need explanation, and how the programme note differs from internal research. It can also list verified reception of earlier productions and translations, clearly labelled as documented reviews or commentary rather than as settled judgement. For touring or international co-production, distinguish the source-culture audience from the receiving audience. Content notes may also be useful where the play deals with sensitive material.

Format and assembly

A tiered format works well: a one-page quick reference for the first day of rehearsal, a main pack with short sections, and an appendix for longer documents and images. Keep citations near the relevant claim, date the pack, and use version control. A classroom brief may set 5–7 pages, while a professional digital pack can be longer and more searchable. Ensure the document is accessible, and include a named contact for questions. Use images only when rights and captions are clear; do not present an unlicensed production photograph as illustrative evidence.

Common pitfalls

  • Treating the translation as transparent and omitting the translator.
  • Confusing source text, target text and adaptation.
  • Presenting one national or linguistic culture as homogeneous.
  • Inventing translator intentions or undocumented production history.
  • Overloading the pack with plot summary and leaving no space for language notes.
  • Ignoring rights and credits until opening night.
  • Treating surtitles or access materials as an afterthought.

A practical checklist

  1. Identify the exact source text, edition and target text.
  2. Credit the translator and outline the translation history.
  3. Map language, place, period, community and register.
  4. List recurring terms, names and pronunciation.
  5. Record translation choices with short, documented examples.
  6. Verify rights, permissions and credit lines.
  7. Collect verified production history and reception.
  8. Prepare images, glossary and further reading with rights information.
  9. Add surtitle or access notes where applicable.
  10. Date the pack, version it, and mark uncertainties clearly.

In short, a good pack for a translated play does not replace the translator’s work or the director’s interpretation. It makes both easier to discuss. It gives the rehearsal room enough context to ask better questions, and enough documentation to avoid treating translation as invisible.

FAQ

Is a dramaturgical pack the same as a programme note?

No. A pack is an internal working document for the production team, while a programme note is written for the audience. The pack may supply material for the programme note, but it usually includes more detailed evidence, uncertainties and rehearsal questions.

Should every translated-play pack include a full translation history?

No. Scale the history to the production. At minimum, identify the translator, source edition and status of the translation. Add verified prior translations or productions where they help the team understand the text or its reception.

How long should a dramaturgical pack be?

There is no single rule. One university dramaturgy brief sets 5–7 pages, which is a useful exercise in concision. Professional packs are often tiered: a short quick-reference section plus a larger digital appendix.

What if there are no published translator's notes?

Do not invent them. Record what is documented, mark open questions clearly, and, where possible, invite the translator to comment. The pack can distinguish editorial interpretation from the translator's own stated choices.

Who is responsible for translation rights and credits?

The producer or rights holder should verify rights and credit requirements. The dramaturgical pack can record the relevant credit line, rights holder and questions, but it does not replace legal or contractual clearance.

READ FURTHER

Sources & references

  1. Baruch College, Dramaturgy Packet, Theater History Spring 2016, https://blogs.baruch.cuny.edu/theaterhistorys16/?page_id=681
  2. Magda Romanska, Dramaturgy Student Handbook, Emerson College, https://www.lmda.org/sites/default/files/MadgaRomanskasDramaturgyHandbookforEmerson.pdf
  3. Abbey Theatre, Translations Resource Pack, 2022, https://www.abbeytheatre.ie/wp-content/uploads/2022/09/AT22_Translations_Resource-Pack_final.pdf
  4. Kristi Good, Best Practices for Selecting a Translated Script: A Dramaturg's Manifesto, Theatre Topics, 2017, https://doi.org/10.1353/tt.2017.0040

THE LANGUAGE OF PRACTICE

Related terms

Dramaturgy
Research and communication that supports a production's interpretation and rehearsal process.
Source text
The text in its original language from which a translation is made.
Target text
The translated text produced for the receiving language and culture.
Translator's note
Commentary by a translator on choices, omissions or contextual issues in a translation.
Surtitles
Projected translation of spoken or sung text during a performance.
Production history
A documented record of previous stagings, translations, adaptations and reception.

A SHARED BODY OF KNOWLEDGE

Something to add or correct? Help us keep the conversation informed.

Corrections & updates

Leave a Reply

Your email address will not be published. Required fields are marked *

THE CONVERSATION CONTINUES

Keep a window open to the world.

Fresh perspectives and practical reading, straight to your feed reader.

Subscribe via RSS

FOLLOW YOUR CURIOSITY

Find your next idea.

Search the journal, practical guides, and pages.

THE PRACTICAL TOOLKIT / 01

Your first conversations.

Use these prompts to begin planning with your collaborators. Your progress is saved in this browser.

A starting point for discussion. Adapt it to your project and check local requirements with the relevant organisations.

THE PRACTICAL TOOLKIT / 02

A time to come together.

Choose a date and time in UTC to see when your collaborators would meet. Times account for daylight saving on your chosen date.

Shaded times fall outside 09:00–18:00 local time. Agree working hours and access needs with your team.

BEHIND THE IMAGES

Photography credits

Editorial stock photographs illustrate themes; they do not document the productions discussed on this site. Used under the Pexels licence.