HIERARCHICAL_JSON
{ 'key' : 'translation'}
MULTILINGUAL_JSON
{ 'locale' : { 'key' : 'translation "}}
HIERARCHICAL_JSON_PRETTY_PRINT
This format can ONLY be exported. The content is the same as HIERARCHICAL_JSON but with human-friendly indentation.
{
'key' : 'translation'
}
I18NEXT_HIERARCHICAL_JSON, I18NEXT_MULTILINGUAL_JSON
These are two well-documented formats of the i18next library format that support plurals and gender.
HIERARCHICAL_JSON vs MULTILINGUAL_JSON (during export)
When using MULTILINGUAL_JSON, there is only one file for all languages.
When using HIERARCHICAL_JSON, there wlil be a file for each language as follows:
**en/translation.json** or **en.json**, depending on the parameters used in API
{ 'key' : 'english source text'}**fr/translation.json** or **fr.json**, depending on the parameters used in API
{ 'key' : 'french translation'}
Comments
4 comments
JSON has eclipsed XML as the preferred data interchange format for web applications and Although JSON is derived from JavaScript, it is supported either natively or As noted above, the main alternative to JSON is XML.
walgreenslistens
Jsnon has always been supportive, it is supported either natively or As noted above, the main alternative to JSON is XML.
it is supported either natively or As noted above, the main alternative to JSON is XML.
www.telltims.com
Are we allowed to give empty lines in the JSON(en.json, fr.json) files? Do you charge for them as well?
Can you explain this brief?
Please sign in to leave a comment.