-
☆ A M B ☆
- 24,524 Posts
I am finding the Context+Babel method of handling multi-language sites to be awkward and unsatisfactory. It seems to me that there could be a Custom Resource that uses lexicons for the resource text fields. Almost like YAMS for Evo uses TVs. No need for plugins or web server rewrites, just a SESSION and/or COOKIE value for the language the user selects, or his browers prefers, and then use [[%pagetitle]], [[%content]] etc instead of [[*pagetitle]] and [[*content]]. Maybe a plugin to switch lexicons. The details are still a bit hazy. Thoughts?
I think this would be a great idea to persue! Also not really happy with the current internationalisation possibilities, Babel is more or less the only thing that works for this and handling it through MODx lexicons would be far more "native". So would you still have a resource for every language (which would probably defeat the purpose right?) or how do you think the different language strings would be handled (inputs)?
-
☆ A M B ☆
- 179 Posts
Quote from: exside at Jan 31, 2013, 04:20 PMAlso not really happy with the current internationalisation possibilities./quote]
I use a project lexicon to store all lanuage depentend information, like start IDs for certain sections or headlines and what ever. Here a life example, complete done without babel, because the language trees are not 1:1 translations: http://www.inbs-online.com
I would really love to have a separate user lexicon. At the moment, you can either have access to all the lexicons or to none, but it is not possible to unlock just one lexicon to be editable by a user. I would not want my clients to mess around in the core lexicon but would love if they could edit their own foreign languages text.
I think you could give a user access to a lexicon with Media Sources, but I've never tried it.
Also, you can use a snippet or a plugin with $modx->lexicon->load() to load any lexicon files you want. They'll overwrite whatever is in memory.
-
☆ A M B ☆
- 24,524 Posts
I envision something like the YAMS for Evo; it uses TVs for each language, and uses ManagerManager to put each language's set of TVs in its own tab. The difference would be that the tabs would be to edit fields for lexicon files instead of TVs. My main issues are to avoid the use of web server rewrites, minimize plugin requirements, and of course get rid of the redundant pages in the contexts. It would also simplify the various dynamic text that needs to be displayed, like menus, form labels, messages, what-have-you. Simply replacing the usual tags with lexicon tags would take care of it all, once a lexicon is set.
-
☆ A M B ☆
- 24,524 Posts
Interesting. Thanks for the link. Why do you say "abandoned"? September is only four months ago.
