plc.jbc.lol / wf.jbc.lol
A modified version of Wafrn used on https://wf.jbc.lol (mirror of https://git.jbc.lol/jbcrn/wf.jbc.lol which is a mirror of https://codeberg.org/jbcarreon123/wf.jbc.lol)
fork atom
wf.jbc.lol / docs / translation.md
at preproduction 2.2 kB view raw view code
plc.jbc.lol another things
5b17bd8e

Translating Wafrn#

Wafrn translations are done via JSON files located at packages/frontend/src/assets/i18n/. The primary language of Wafrn is English so there are a lot of small places where the translation files are not used yet.

Note that adding languages is not as simple as creating the JSON file, you must follow the steps under the header Enabling a language on the frontend due to technical reasons.

Contributing to an existing language#

First, locate the language you wish to add translations for in the packages/frontend/src/assets/i18n/ folder. The language should be stored under its country code as a JSON file.

The translations on the en.json file are often not matched on other translation files due to being constantly updated. To add the missing keys, use the following commands:

npm run frontend:translations:patch -- YOUR_LANGUAGE_HERE.json
npm run frontend:translations:format

After this, you can edit the new translation keys and contribute through Git commands as normal.

Adding a new language#

To add a new language, copy the current en.json with a new name from the country code. You may abbreviate to just the first part if there are no others under that name. Then simply use the English file to translate.

If you would rather start from a different language, follow the header Adding a new language to patch the language you wish to start from, then run:

npm run frontend:translations:patch -- THE_LANGUAGE_YOU_ARE_STARTING_FROM.json YOUR_NEW_LANGUAGE.json

You should now have a JSON file with up-to-date keys which you can start to translations on.

Enabling a language on the frontend#

Languages are enabled in packages/frontend/src/app/lists/languages.ts by adding them to the variable supportedLanguages and then filling out the variable languageMap with its native name.