Lots of people use more or less simple json formats for i18n. E.g. apertium-html-tools
{
"@metadata": {
"authors": [ "Juan Pablo Martínez Cortés" ],
"last-updated": "30/01/2016",
"locale": [ "arg" ],
"completion": " 96% 106.82%",
"missing": [ ]
},
"title": "Apertium | Una plataforma libre de traducción automatica",
"tagline": "Plataforma de traducción automatica lliure/de codigo fuent ubierto"
}
or "professional" formats like https://www.i18next.com/misc/json-format
The typical format seems to be a simple object of {key:string-to-be-translated}. If transfuse could handle that simple format (ignoring the advanced i18next stuff, and skipping anything where value is not a string), we'd probably have support for most of the json-using i18n's.
Lots of people use more or less simple json formats for i18n. E.g. apertium-html-tools
or "professional" formats like https://www.i18next.com/misc/json-format
The typical format seems to be a simple object of
{key:string-to-be-translated}. If transfuse could handle that simple format (ignoring the advanced i18next stuff, and skipping anything where value is not a string), we'd probably have support for most of the json-using i18n's.