We have JSON schema files specifying the shape of our templates, patterns and tests configuration files.
These files include "title" and "description" properties which are used to generate a form with json-editor, easier to edit than manually writing a JSON file.
However, these "title" and "description" properties have values in English only.
Consider having a set of master schema files from which a series of translated schemas are automatically generated (e.g., es.templates.json.schema).
Consider having a set of master schema files from which a series of translated schemas are automatically generated (e.g., es.templates.json.schema).
I guess this could be done upon compiling the source code, or even better (for more immediate availability of translations) browser-side. That is, the browser would download both the master/main file and the corresponding translation file, and generate the final translated schema on the fly.
We may consider moving these messages from schemas in Web2Cit-Core to some complementary or overriding logic in Web2Cit-Server for more straightforward translation once T408866 has been solved.
Internationalized JSON schemas in Web2Cit-Core with 50923c69.
We may consider moving these messages from schemas in Web2Cit-Core to some complementary or overriding logic in Web2Cit-Server for more straightforward translation once T408866 has been solved.
Supported localization of internationalized JSON schemas in Web2Cit-Server with 7060810e.