uptime-kuma/src/languages/README.md
Matthew Nickson f67d7cdf3f
Make update-language-files command more useful (#2198)
* [empty commit] pull request for Fix language update script

* Avoid mass changes with update-language-files

This commit updates the update-language-files script to prevent mass
changes as seen on a number of recent PRs where the contributer has
ran the script and comitted the results.
The script has been updated to now require the --language argument to
specify which language file to update. This ensures that only that file
is updated instead of all files. If the provided language code does not
already exist, a new file with that code is created. This should make
it easier to add new languages as you only need to pass the language
code to the script.
The base lang code is now also passed as an optional argument to negate
the need for a seperate script entry in package.json.
The script has been restructures into a couple of functions to make it
easier to understand.
ESlint now only checks the changed file instead of
them all in order to improve performance.

Signed-off-by: Matthew Nickson <mnickson@sidingsmedia.com>

* Updated translation docs for new command

Signed-off-by: Matthew Nickson <mnickson@sidingsmedia.com>

* [update-language-files] Add cross-env-shell

Signed-off-by: Matthew Nickson <mnickson@sidingsmedia.com>
Co-authored-by: Louis Lam <louislam@users.noreply.github.com>
2022-10-08 15:01:47 +08:00

647 B

How to translate

  1. Fork this repo.
  2. Run npm run update-language-files --language=<code> where <code> is a valid ISO language code: http://www.lingoes.net/en/translator/langcode.htm. You can also use this command to check if there are new strings to translate for your language.
  3. Your language file should be filled in. You can translate now.
  4. Add it into languageList constant.
  5. Make a pull request when you have done.

If you do not have programming skills, let me know in the issues section. I will assist you. 😏