The Programme’s Second Language: Translation Gaps and Interpreting Labour in the Manchester 2013 Record

International conferences are often described as multilingual spaces, but their paper records tend to be monolingual. The Manchester 2013 archive is no exception. Its programme, abstracts and related materials are predominantly in English, with translated session titles appearing unevenly and interpreting arrangements visible only in fragments. For 2026 seminar organisers, those fragments are worth reading carefully. They show that language access is not a decorative addition to an international event; it is part of the event’s infrastructure, and its absences leave marks in the archive.

What the archive actually holds

The first task is descriptive rather than accusatory. The Manchester 2013 record contains abstracts submitted in more than one language, but the balance is heavily weighted towards English. Some session titles appear in translated form, sometimes as a courtesy, sometimes as a practical aid, and sometimes not at all. Interpreting arrangements are harder to reconstruct: they may appear in logistical notes, room allocations or correspondence rather than in the published programme. A 2026 reader therefore has to distinguish between what was provided, what was advertised and what survives in the record.

That distinction matters. A conference can be multilingual in practice while its archive remains largely English. Conversely, a programme can list translated titles without any interpreting provision at all. Reading the Manchester 2013 materials against one another makes these differences visible, and it prevents us from assuming that the language of the archive is the language of the event.

Reading gaps as evidence

Gaps are not simply missing data. They are patterned. Which languages appear in the abstract book? Which sessions carry translated titles? Are translations literal, summary or promotional? Does a translated title suggest that the session was expected to attract speakers or audiences beyond English? These questions turn the archive into a map of institutional priorities, however partial.

A useful method is to build a simple three-column table for each session: the English title, any translated title, and any note on interpreting or language access. The table will quickly show where translation was routine and where it was absent. It will also show how often translation was limited to the title rather than the abstract or the presentation. For 2026 organisers, that is a practical lesson: announcing a multilingual event is not the same as designing one.

The interpreter’s invisible chair

The interpreter’s chair is a useful figure for the archive because it names labour that is often present but unrecorded. Interpreting requires preparation, terminology work, timing and close attention to speaker rhythm. It also requires someone to be in the room, often without appearing in the programme. When the archive records interpreting arrangements only indirectly, it reproduces a wider pattern in which language work is treated as background support rather than intellectual contribution.

This is not a reason to read bad faith into every omission. Conference organisation is constrained by budgets, deadlines and institutional capacity. But it is a reason to ask better questions of old programmes. Who was expected to translate? Were speakers asked to provide translated abstracts? Were session chairs briefed on working across languages? Was interpreting available for plenaries only, or for parallel panels too? The answers may be incomplete, but the questions clarify what a genuinely international event requires.

A practical protocol for 2026 seminar organisers

For those designing international seminars in 2026, the Manchester 2013 record suggests a short planning protocol. First, state the language policy explicitly in the call for papers: which languages are accepted for abstracts, which languages will be used in sessions, and what support is available. Second, budget for interpreting and translation as core costs, not optional extras. Third, ask for translated titles at the point of submission, and publish them alongside the English title where provided. Fourth, brief chairs on multilingual chairing, including how to manage interventions and time. Fifth, record language provision in the final programme so that future archives can show what was actually offered.

There is also a documentation lesson. If a seminar provides interpreting, the programme should say so clearly, and the archive should retain that information. Otherwise, the event’s multilingual labour disappears from the record, and later readers are left to infer it from scattered notes. For UK-based organisers working with international partners, this is a modest but meaningful way to make access visible.

What the old programme teaches

The Manchester 2013 archive does not offer a model of perfect multilingual practice. It offers something more useful: a record of uneven provision that can be read as a design brief. The translated titles show that language was considered; the English-heavy abstracts show that consideration was limited; the fragmentary interpreting notes show that access depended on logistics that were rarely documented.

A 2026 seminar need not repeat that pattern. By treating translation as part of the intellectual architecture of an event, and by recording language provision as carefully as room allocations or panel times, organisers can make the interpreter’s chair visible. That is not only a matter of courtesy. It is a condition of the international conversation that conferences such as Manchester 2013 were meant to enable.