-
☆ A M B ☆
- 24,524 Posts
Well, the first multi-language site I made was done that way, using SESSION and COOKIE to maintain the language the user selected, storing the parent resource ID.
Eventually I got tired of constantly updating four different pages every time the client got a new employee, and started using TVs for each language, using a prefix like en_pagetitle for each TV.
Then I discovered YAMS for Evo, which uses TVs and adds a whole bunch of snippets and plugins to manage the whole business.
The last multi-language site I did was on Revo, using contexts and Babel. It was a pain in the neck, and I never did get the Gallery add-on set up for multi-langauge.
I have in mind to develop a system using MIGXdb and lexicons that will be much simpler.
But for just a few pages, and not much in the way of content, you might be best off using just lexicons. Set the correct locale and language in a plugin.
-
☆ A M B ☆
- 24,524 Posts
No, it's just something I've been considering quite a bit lately. I'm just waiting for the beta release of 2.3. So far what I've seen of it is really impressive, but it will definitely have some differences that will need to be taken into account.