diff options
| author | Pliable Pixels <pliablepixels@gmail.com> | 2019-03-16 07:11:54 -0400 |
|---|---|---|
| committer | Pliable Pixels <pliablepixels@gmail.com> | 2019-03-16 07:11:54 -0400 |
| commit | 44316ecd150b6c37cb62b9a1c53226f0325f4419 (patch) | |
| tree | 1b211854cf49be8ee4b5bd18e2be899b50545042 /docs/docgen/html/_sources/guides/contributing-language.rst.txt | |
| parent | a59caa2359533fb99dba99e3526795ec76727a52 (diff) | |
changed paths
Diffstat (limited to 'docs/docgen/html/_sources/guides/contributing-language.rst.txt')
| -rw-r--r-- | docs/docgen/html/_sources/guides/contributing-language.rst.txt | 60 |
1 files changed, 60 insertions, 0 deletions
diff --git a/docs/docgen/html/_sources/guides/contributing-language.rst.txt b/docs/docgen/html/_sources/guides/contributing-language.rst.txt new file mode 100644 index 00000000..68f11fd2 --- /dev/null +++ b/docs/docgen/html/_sources/guides/contributing-language.rst.txt @@ -0,0 +1,60 @@ +Contributing a new language +--------------------------- + +If you are familiar with using git, I'd prefer if you follow the Pull +Request process +`here <https://github.com/pliablepixels/zmNinja/blob/master/CONTRIBUTING.md#steps-for-code-contribution>`__. + +Adding a new language +^^^^^^^^^^^^^^^^^^^^^ + +- Languages translations are available + `here <https://github.com/pliablepixels/zmNinja/tree/master/www/lang>`__ +- To contribute a new language, add a new ``locale-xx.json`` (where + ``xx`` is your language code). +- Ideally, you should also provide a language translation for the + zmNinja help file inside + `lang/help <https://github.com/pliablepixels/zmNinja/tree/master/www/lang/help>`__ + +The best way is to simply look at an existing language translation and +follow the same model for yours. If any language translation keywords +are missed, it will fallback to English. + +Main Language file +^^^^^^^^^^^^^^^^^^ + +- Make sure there is no comma after the last element +- Comments are not allowed +- Make sure you don't add ellipsis "..." anywhere, they are added to + messages in code when needed +- After you complete the translation file, do the following: + +(replace ``-it`` with the language you are working on) + +``python ./checklang.py -f locale-it.json -b`` + +This validates your JSON file, makes sure all keys are in sync with -en +and if valid, creates pretty-locale-it.json. If you are sure it looks +good, + +``python ./checklang.py -f locale-it.json -b -o`` + +This validates your JSON file,makes sure all keys are in sync with -en +and if valid, OVERWRITES your local file with a pretty formatted +version, which is what you should PR + +Translating Help language file +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +- Located inside lang/help +- Please be careful not to mess up the html tags, please only focus on + text translation + +How to recognize a new language: +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +(This is only for zmNinja developers. Not relevant for language +translators) + +- Modify languages array in NVR.js (look for ``var languages``) +- Register language glob code in app.js - make sure its added to array list and mapping (look for ``registerAvailableLanguageKeys``) |
