Translations management CLI

[lyyder]

Adds a command line tool that can be used to manage translations:

• see what keys are missing compared to English translations
• add a missing translation

Testing

To try the out the tool, copy src/translations/en.json to src/translations/es.json for example and remove a few lines from the es translations file.

[lyyder]

Let's see at what point we get the default languages translation files added to the project. Not the tool expects to have es, de, and fr translations in place. Maybe all the language definitions could be removed and added as the corresponding files are added. That way this could be merged now without waiting for the translations to finish.

[Gnito]

It's probably better to not use require to future-proof this since "Require is synchronous function and is called only once, which means the calls receive a cached result. If the file is updated you can't re-read it using this method"

https://stackabuse.com/reading-and-writing-json-files-with-node-js/

[Gnito]

@lyyder how about reading current files from the folder?

$ cat asdf.js 
const testFolder = './src/translations/';
const fs = require('fs');

fs.readdirSync(testFolder).forEach(file => {
  console.log(file);
})
$ node asdf.js 
en.json
es.json

Then it would use your TARGET_LANGS for printing names (es -> Spanish) but it would default to language code extracted from file name (found file fi-FI.json -> no known name -> ´fi-FI´)

This way we don't need to keep track any specific translations and customizers could simply delete unnecessary files.

[Gnito]

Looks good to me!
You probably should ask from Thomas if the usage is clear and if color codings work.
And it might be good to check that our translators know when to use this (i.e. this is more beneficial to our customizers when they are updating from upstream - Thomas et. al could use WTI if they prefer that).

[lyyder]

@Gnito I've split the execution based on comments form @thomasmalbaux so that after translating a key the app returns to the missing keys list instead of languages list. This works better when syncing one translations file with the source lang, which is the case with our customizers.