-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
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
Custom Language Files (Idea) #5
Comments
This is planned, I have yet to find an easy to implement solution to this. I need to find the time to go back and convert any strings to translation files. |
Started working on i18n support, chose to go without the composer package as a number of things had to be changed.
so each module would just append to the "modules" key and shouldn't ever affect each other. If you like this, i'll continue down this path, create a PR and push it out. |
module.json needs to be abandoned for textual things like menus if you want language files. Currently looking into a workaround solution. |
Think I solved this by following the idea laid out in loggedin.hooks.php, if the modules use hooks to provide the "info" array, then we can use PHP functions against the text and get back to supporting multiple languages. |
I find it a good idea to invite separate language files to invite texts.
for example
instead of
and say there would be a language folder where there would be a garage.php file whose content
From the language file you have been called to get the garage php file for all the text.
The text was updated successfully, but these errors were encountered: