Translation catalogs for COMP/CON, the digital companion for the LANCER TTRPG. This repo is translation data.
Translations are managed through Weblate. You should not submit to this repo directly to translate. This repo is where Weblate stores its work and where the app reads finished translations from.
- English is automatically generated.
ui/en.jsonarrives as an automated pull request (branchautomated/locales-sync) opened by the app repo's CI whenever UI strings change ondev; merging that PR is what updates the English source in Weblate. Content English is generated from@massif/lancer-data. - Weblate pulls new/changed English source strings and flags affected translations as "needs editing."
- Translators work in Weblate.
- Weblate commits translations back as pull requests to the
weblatebranch.
See CONTRIBUTING.md
Third party content packs are not translated here. Instead, a pack author or translator ships a language patch (.llp) that COMP/CON installs alongside the pack. build-lcp.mjs generates these. COMP/CON CI keeps keys aligned:
curl -O https://raw.githubusercontent.com/massif-press/compcon-locales/master/build-lcp.mjs
# 1. extract every translatable string from an unpacked LCP (the folder containing lib/ or the *.json files)
node build-lcp.mjs extract ./my-lcp --lang fr --out my-pack.fr.llp
# 2. translate the values under "data" and fill in "translator"; leave the keys alone
# 3. distribute the .llp on its own, or add it to the .lcp so both install as one file
node build-lcp.mjs bundle my-pack.lcp my-pack.fr.llpextract takes a directory, so packaged .lcp files must be first extracted. If you already have a flat "<id>.<field>": "text" JSON map, node build-lcp.mjs pack fr.json --target <pack-id> wraps it in a .llp header.
Users install a .llp from the same screen as a .lcp.
GPLv3, matching COMP/CON. Translations contributed via Weblate are licensed under the same terms.