to translate:

task 1
change old wording

just edit schemaLang.json
Note:
while in browser
- name of element is defaulted for TitleEN.
- any absent titles replaced by TitleEN
- any absent Description defaulted to Title
- absent "enum" defaulted to English, (enumEN are obligatory)
- wording from "schemaLang.json" overrides wording from "schema.json", if any.
(translations set to "---" are ignored)


task 2
update schemaLang.json to include new features (and new proposed wordings) added to schema.json

update schema.json from cloud as usually
open in browser through web-server not usual localhost:8082
but localhost:8082/i.htm
now you have dot (".") next to red "online" field.
click it, new buttons would appear
use "save Schlang"
new saved file has "---" for all translations not set in old "schemaLang.json" or current "schema.json"
enjoy


task 3
add new language

edit schemaLang.json, add new abbreviation in "languages" section
please use ISO/IANA abbreviations (2- or 3-letter), if possible, avoid long "dialect" language extentions.
after that, follow "task 2" procedure, you will got "---" placeholders for new language.
leave unchanged if ok to use defaul enflish wording.
