You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: