We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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?
The text was updated successfully, but these errors were encountered: