Skip to content

Translating kindling

kindling’s interface is translated into seven languages, and native speakers are warmly welcome to make each one better. Most of the current translations have not yet been read end to end by a native speaker, so even small corrections help: an awkward phrase, a term writers in your language would never use, or a label that gets cut off.

LanguageCodeCatalog
English (source)enlocales/en
简体中文zh-CNlocales/zh-CN
Españoleslocales/es
Português (Brasil)pt-BRlocales/pt-BR
Русскийrulocales/ru
Deutschdelocales/de
Françaisfrlocales/fr

To see the app in a language, choose it in Settings → Appearance & Guidance → Language. See Language for how kindling picks one by default.

You don’t need to touch any code. Send a screenshot and the wording you would suggest through any of these:

Each catalog is a folder of plain TypeScript files of key: "text" pairs, grouped by part of the app: sidebar.ts, settings.ts, export.ts and so on. Edit the text on the right and open a pull request.

  • Keep every {placeholder} intact. {count}, {title} and the like are filled in by the app. Move them wherever your language needs them, but don’t translate or remove them. A test fails on a missing placeholder.
  • Counts have one entry per plural form. English has .one and .other (1 scene, 3 scenes). Your language has the forms it uses for whole numbers: Russian has .one, .few and .many; Chinese has only .other. Translate each form you find.
  • Use the glossary. The interface glossary records how each language renders core terms like beat, scene and reference, so the same idea reads the same way everywhere. If you think a term is wrong, change the glossary in the same pull request as the catalogs, so the whole app stays consistent. Some terms are still open, such as the Spanish beat.

Wanted: Traditional Chinese (zh-TW). Systems set to Traditional Chinese currently read the Simplified Chinese interface. If you can translate into Traditional Chinese, we’d love to hear from you.

Adding a language needs a catalog, its plural forms, a registry entry, the native menu labels and the glossary column. The steps are in Internationalization in the architecture notes. Start by adding a column to the glossary, then copy the English catalog. Components don’t change.

If you’d like to take on a language but would rather not set up a development build, open a discussion first and we’ll work out the rest together.