diff options
| author | Pliable Pixels <pliablepixels@gmail.com> | 2016-12-04 20:24:11 -0500 |
|---|---|---|
| committer | Pliable Pixels <pliablepixels@gmail.com> | 2016-12-04 20:24:11 -0500 |
| commit | f012faaaf9075a362708a77d3d465c2eeb4f5d42 (patch) | |
| tree | 940221f2faa6f06de29ab920e49a36e747160dd4 | |
| parent | 39b80e16a03b7453cd8211f293176be0a58d9a37 (diff) | |
updated
| -rw-r--r-- | www/lang/README.md | 11 |
1 files changed, 1 insertions, 10 deletions
diff --git a/www/lang/README.md b/www/lang/README.md index 5215a8dc..b2737f3c 100644 --- a/www/lang/README.md +++ b/www/lang/README.md @@ -16,27 +16,18 @@ The best way is to simply look at an existing language translation and follow th (replace ``-it`` with the language you are working on) -Python 2.x: + `` ./checklang.py -f locale-it.json -b `` -Python 3.x: -`` -./checklang.py3 -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 2.x: `` ./checklang.py -f locale-it.json -b -o `` -Python 3.x: -`` -./checklang.py3 -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 |