We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 38793
    • 18 Posts
    Hi,

    I am using Revolution to currently design a small art portfolio website which will be in English and Japanese.

    I have read most of the tutorials about setting up modx revo using a different contexts for each Language. I followed the http://designfromwithin.com/blog-webdesign-development/2012/01/12/modx-multilingual-setting-up-babel-and-have-a-website-with-multible-languages/ tutorial but didn't use Babel to manage the translations as I can do them manually seeing as the website is only small.

    I got this method working but came across certain linking problems when using the rich text editor.

    What I want to ask is, what are the advantages (for me in this case) in using different contexts for each language when I could just make a folder in the web context call it "Japanese" and give it an alias of "ja" make it a container, thus giving me the following url www.mysite.com/ja/home.htm. I could understand maybe if I had lots of languages then having many Contexts set up would have its advantage, but in my case would I see an advantage of setting up different contexts?

    maybe this is one of them questions where what suits you better works, just thought I would ask.

    thanks for reading,

    Tim

      • 28042 ☆ 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.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 38793
        • 18 Posts
        Thank you for the feedback.

        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.

        This is what got me to ask my question, as I would install/use an addon which would throw up some other problem which I would have to figure out how to fix or ask here in the forums; due to not having the skills to fix the problem myself.

        you might be best off using just lexicons. Set the correct locale and language in a plugin.

        apart from the help docs, do you have any links at hand that might be helpful? if not, not to worry

        thank you for replying,

        Tim
          • 28042 ☆ 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.
            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org
            • 38793
            • 18 Posts
            ok, thanks anyway,

            Tim