Open stonymahony opened 2 months ago
Firstly, many thanks for the package, especially the key generation is a lifesaver!
What I wish for would be the support of namespaces as defined in i18n, the advantages are listed there.
Meaning, it should be possible to split the translations into several files for each language.
Example:
/assets/i18n - fr - general.json - navbar.json - en - general.json - navbar.json
Is there any chance of implementing this? How complex is this, does it require major changes to the status quo?
Firstly, many thanks for the package, especially the key generation is a lifesaver!
What I wish for would be the support of namespaces as defined in i18n, the advantages are listed there.
Meaning, it should be possible to split the translations into several files for each language.
Example:
Is there any chance of implementing this? How complex is this, does it require major changes to the status quo?