To update the language files you just need to know a bit of GIT. This page should help with the structure of language files.
There are two places where language override files are stored. The LANG_CODE is the two letter code for that language. Eg: en, fr, de
src/lang/_strings/LANG_CODE.po
msgstr.msgstr for the string, then copy from en.po and update, Eg de.po.msgctxt ""
msgid "Select a filter"
msgstr "Filter wählen"
src/lang/LANG_CODE/PAGE.md
Example: If your new language is French it would have a LANG_KEY of fr.
You also need to tell the application to have it as an option. So you edit this file:
/src/js/helpers/translate.js.coffee and add fr: "French" to the languages in getLanguages
Copy the files you want to override with the new language:
/src/_strings/en.po to /src/_strings/fr.po/src/en/readme.md to /src/fr/readme.mdTo test you need to do a build, however if you follow the existing structure you shouldn't need to.
If do you want to test your language in the app with a build, you can:
nodejs, npm are installedcd /chorus/foldernpm install (only the first time)grunt lang (this will rebuild only the languages in the dist/lang folder)Translations should fallback to English unless the msgid is set in a LANG_CODE.po file.
Or if a page LANG_CODE/PAGE.md exists.
Send a pull request through GitHub on a new branch is the best way. Would consider updates via other methods.