We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 26113
    • 88 Posts
    Hello -
    I’m starting up a new website for a client who needs a site in English & Spanish.
    I’ve never dealt with translations of a website so I don’t know the process of how most sites are done.
    Does modx support any translation or is this done with server software?

    Thanks for any direction on this.
    Rich
      • 10076
      • 1,024 Posts
      Do you mean if there is a way to have it translated automaticly?
      I don´ t think there is any software that translates well enough to use for published text.
      Have a look at http://babelfish.altavista.com/ you will see what I mean.
        • 5699
        • 46 Posts
        computersolutions.cn Reply #3, 19 years, 8 months ago
        Typically the client will provide the translation for you.

        If that is not possible, then you will need to contract a translation company to translate the content for you, and charge the fee’s for that to the client.

        Thats really out of scope for a template question though wink

        For doing multilingual sites, what I usually do is this:

        1) Set the default site language type to a correct encoding - UTF-8 is a good choice.
        2) Make two top level documents for each language, and make them folders (containers in >.95)

        Put the site content for each language in the relevant folders.

        In the template I make hard links to the top level for each language.

        eg - If I make a document id 1 for English, doc id 2 for Spanish, and then put the english under 1... and spanish under 2

        In my template I make a link for the language

        english <a href="/?id=1">english</a> <a href="/id?=2">espanol</a>

        and modx handles the rest.


        Depends on your site structure though, and how mixed the languages will be.
        If its a basic site with content replicated per language, this works well.





          • 31227
          • 198 Posts
          Here is an example:
          http://www.viriko.com/home-en - English site
          http://www.viriko.ru/home-ru - Russian site
          home-ru or home-en can be called on both .com or .ru domain. Basicly it’s the same site.
          The site is using MODx, and subsites, you can call it by ids too but I prefer using furl. Modx (1), 2 containers, 2 templates +1 for intro. The property script also uses 1 db for both Russian & English (love that thingie, took a lot of effort)
            Pure MODx sites
            Viriko.ru & Viriko.com - Multilingual and running on 1 MODx
            • 20289
            • 958 Posts
              [img]http://i10.tinypic.com/52c4eir.gif[/img][/td]
              [td][Wiki] [Persian support forum]
              [SVN] [RTL SVN Branch] [bugs] [FishEye+Crucible] [Learn MODx!] | [My Google Code]
              [font=tahoma][برای دسترسی به راهنمای فارسی به [url=http://www.modxcms.ir]
              • 28182
              • 15 Posts
              Quote from: MotSmart at Mar 02, 2007, 11:51 PM

              have a look on wiki: http://wiki.modxcms.com/index.php/Make_Multi_Lingual_Site
              This is a great method, you can have as many languages as you like cool
                • 27226
                • 186 Posts
                Yep! Very clever! I like it much more than all the clutter that babelfish causes in the backend of J!
                grin

                [EDIT] Hmm, together with my "ReplacePage" thingie - seems that I now have everything I needed to kick J! out: Versioning and multilanguage ... [/EDIT]
                  • 1157
                  • 2 Posts

                  you may get the web site translated automatically , page by page

                  I,ve done so to 15 different languages

                  the best one is spanish

                  I recommend this translator since its the best

                  http://webtranslation.imtranslator.net/#

                  however

                  its best to copy each translated page to your own then publish it
                  this way when their computer breaks down , it does not affect you

                  you can see what I did on my site
                  at
                  http://alkahtane.com/enghome.htm

                  good luck



                  www.alkahtane.com
                  The truth for a change,
                  about the end of time and much more


                    • 30960
                    • 12 Posts
                    Please let me introduce my own solution... (Oh, if I just have seen this topic before!)

                    I made snippet/plugin works together to handle multilingul pages.
                    please see the page below for details.
                    http://nanabit.net/modx/multilingual-listing-en.html
                    (or in Japanese: http://nanabit.net/modx/multilingual-listing.html)

                    First, the snippet Multilingual Listing makes a switching list like the solution above.
                    The difference is, this one searchs identical document but written in other languages by
                    aliases, like ’doc’, ’doc-fr’, ’doc-ja’,.., not by TVs.)

                    Next, the plugin Multilingual Router devides the access by looking up Accept-Language
                    HTTP request header. It attempts to find the document in specified language, and if found,
                    sendForward(..) to it.

                    This function contradicts to the first one, so if the visitor is from same document(but in
                    another language), the plugin does nothing.

                    Finally, the total difference between the solution above and this one is,
                    that the latter enables the site owner to provide alternative language at the pinpoint documents.
                    If my understanding is correct, with the former way, all alternative languages’ page
                    should be provided.
                    In this way, if the requested language version does not exist, the visitor will simply receive
                    the original language version. So they can translate it by their own (with web translation services).

                    I think the former method suits for formal cases that all pages should completely written in the
                    requested language, and this method would suit rather informal and incomplete (yes, the only
                    document-content is alternative. Even though the visitors select another language, templates
                    , chunks and so on do not alter. shocked) cases that the site owners who want to provide to the visitors
                    a glimpse of the document in a few pages.

                    Thanks,