4) Translations management

In the source code

Erdapfel's js and jsx files contain strings that can be translated. The source strings are in English. We translate them in BR (breton), CA (catalan), DE (german), ES (spanish), FR (franch) and IT (italia).

Singular strings are used like this:

const { _ } = useI18n();
_('string', 'context')

Plural strings are used like this:

const { _n } = useI18n();
_n('%d item', '%d items', itemCount, 'context')

In Poedit

Once the source strings have been pushed and merged on the main (master) branch, they can be translated using Poedit.

Poedit configuration

• Disable MO file generation: File > Settings > disable the MO checkbox

• Add the xgettext --no-location parameter in Translation > Settings > Translation Properties > Advanced Extraction Settings

• Check the paths in Translation > Settings > Paths The correct paths are: /src, /views, /public/build/javascript/bundle.js and /public/build/javascript/map.js (they should already be correct, if not you can select the correct folders again)

• Update the PO file by clicking "Update from the code":

Translating

• Show the untranslated strings first using the Display > "Errors first" / "Untranslated first" options:

• Fill all the blanks in the PO files (except en.po) using your native tongue or DeepL
• Create a branch with these edits, push the updated PO files, and open a Pull Request on Github
• A teammember will merge the PR.