I’m relatively new to modX. Can anyone point me to, or post a survey of the different solutions for making a MODx site multilingual? When one sees things like "Yet Another Multilingual System", it creates an image of dozens and dozens of different approaches. But I haven’t been able to find a good summary or list.
Which ones do you like?
Which ones are strongly supported?
Many thanks,
Alex
-
☆ A M B ☆
- 24,524 Posts
There’s basically three approaches (as far as I know). One is for Evo, one for Revo, and one will work with either one.
The simplest method is to just have top-level resources as containers for each language, using SESSION and/or cookies to keep track of the user’s language choice, and/or using something like UltimateParent to determine the top-level parent of the section the user is in, which determines what language he’s viewing in.
For Evo there is YAMS. Unfortunately, while the latest released version works well, the developer no longer has time to support it, and until someone can have the time to get into it thoroughly enough to take over support and further development, that’s as far as it goes. The concept of a set of TVs as translated content is convenient (I had used this for a FAQ-type list before I was aware that YAMS did it), but by itself it leaves a lot to be desired, which is why YAMS has morphed into a major app in its own right.
For Revo there is the concept of "contexts", which while not as convenient for editing as YAMS, is very flexible and powerful.
