Skip to content
Recluse Studio
← Field notes

Translation changes the edition

Italian CBR+PNK, Outline and Cairn show why language editions need their own component, version and contributor records.

Two open pamphlets face each other, joined by a loose strand of green ink across white scratches and purple washes on near-black paper.
Original illustration / OpenAI image generation

The Italian publisher of CBR+PNK Augmented lists material created specifically for its edition, including Marta Palvarini’s €UROVENICE, alongside player sheets supplied in gatefold and A4 printing formats for the edition’s readers. The edition has a local publishing shape as well as a language. Grumpy Bear’s listing

That makes translation an edition question from the outset. A library selecting a language version needs to know which rules, adventures and aids it contains. A familiar title and cover cannot answer those questions on their own.

I read the Italian listing with machine-assisted translation and am using its explicit product and credit information. I have not compared the complete language editions, assessed their translation quality or verified every advertised component against delivered files.

Start with the edition that a reader will receive

The listing credits Emanoel Melo as author and MythWorks as original publisher. Its named Italian contribution shows why the record should also retain local creative work. Describing the whole package simply as an Italian copy of the original could conceal material a researcher or player specifically wants to find.

A translation may also be based on a particular revision of the source game, which means that a subsequent change in the original can leave the translated edition changing later, differently or not at all. The relation needs checking through dated releases or publisher statements rather than an assumption that all language routes stay synchronised.

Outline makes that question visible in another way. Its creator lists English and Brazilian Portuguese routes and says future changes will appear first on the official website. A downloadable manual, a web text and a translated route therefore need to be identified individually when the library records what it has consulted. Outline’s publication page

This is a question about evidence, not a prediction that the versions disagree. A record can state the language, version and date checked without claiming a comparison that staff have not performed. That modest precision gives a later reader a useful starting point.

Translation involves production choices

The Cairn localisation guide recommends beginning from the SRD and describes routes into a translated document, a language-specific website and layout files. It asks for the language version to be identified on the cover. The guide makes visible several pieces of work around the translated wording.

A change in language can affect line lengths, headings and references. A rule that fits beside a diagram in one edition may need a different arrangement in another. These are possible production problems that a particular edition must resolve, rather than defects established merely by its being translated.

The work can involve translators, editors, proofreaders and layout contributors, with responsibilities distributed differently from one project to another. Becker’s account of art as collective action helps make that coordination part of the publication’s history instead of treating every contribution as an invisible service to the original author.

Credit should follow evidence. Where a publication names a translator, retain that role. Where the available listing names only a publisher, do not invent the person who performed the translation or assume that the publisher’s owner did the work. A request for missing information can be specific and limited.

A catalogue can express the relationship without erasing the difference

The IFLA Library Reference Model distinguishes a work from its expressions, manifestations and individual items. Those distinctions help a cataloguer think about language, publication form and the copy held. They do not remove the need to inspect how a package combines translated and newly created material.

For the Italian CBR+PNK package, a useful description would preserve its language and edition identity, then identify significant additional content and its credited creator. The exact record structure should follow the institution’s cataloguing practice and the evidence in the acquired publication.

Discovery also needs the terms readers use. A translated title, an original title and a familiar system name can each be useful routes. Linking them should help readers reach the available edition while allowing them to see which language and components they are choosing.

The distinction becomes practical when a patron requests a particular adventure. A library may hold a related package that lacks that adventure, or a language edition that includes it under another title. The staff member needs component information, not merely confirmation that the broad game title appears in the catalogue.

Language access requires a real reading route

A public library serving readers in several languages can begin with expressed needs and relevant community relationships. Selecting a translated game is useful when readers can also find the instructions, aids and support needed for the intended use. The library should establish that route before advertising a session in a language it cannot support.

An academic library may have a different purpose. A translation seminar could compare a short, permitted passage and ask how its instructions distribute action or authority. That activity needs people qualified to read the languages and enough context to distinguish translation choices from revisions in the underlying game.

Machine assistance can help staff locate a title or understand a basic listing. It should not silently become a claim of expert evaluation. The acquisition record can say which parts were checked and which require a competent language reader before a more specific recommendation is made.

I would also keep the contributor question open during programming. If a translator is invited to explain their work, that is professional participation with its own time and preparation. The invitation should recognise those demands rather than treating the translator as a convenient supplement to the book.

Keep the local publication visible

The Italian CBR+PNK example gives a simple reason to resist flattening language editions into one interchangeable object. A local edition can add a place, an author and a particular arrangement of materials to the game’s circulation.

Recording those details helps a player obtain the right components and helps a researcher follow how the game changed as it travelled. Translation becomes visible as publishing work, with people and choices that deserve to remain attached to the edition readers actually use.