Languages

A translation is not a second deck. It is a layer over the one you have, and only the cards that differ carry anything.

How it works

A project names its content languages, the first being the one the cards were written in. Translations are stored per card, so a card whose title is translated but whose artwork tweak is not gets both, and a card with no translation at all falls back to the original wholesale.

Pick the active language and the editor shows the deck in it. What you type routes by what kind of property it is:

• Content — what a card says: text, an artwork path, QR data — lands in the active language.
• Layout — geometry, fonts, colours — always lands on the blueprint, shared by every language, because a German card is not a different design.

Clearing a translated value drops the translation and lets the original show through.

Translating in a spreadsheet

A translator does not need Boardsmith. Data ▸ Export Project Excel writes each language as a sheet of its own beside the deck's — Heroes@UK next to Heroes — and Import Project Excel lays what comes back onto the cards. A translation sheet only fills in cards that exist: a new card goes on the base sheet first, and its translations in the same file land on it. Translation sheets never delete anything.

Exporting

Every export carries the language in its file names, so two languages' files land side by side rather than overwriting each other.

Removing a language

Taking a language off the list only hides it from the picker. The translations stay in the cards, and adding the language back finds them again.