Babel or migxmultilang?

Until now I always use Babel for multilanguage website. In the Modx Revolution Extra Digest I read about migxmultilang (by Bruno17), but it seems like a total other approach then working with Babel.

I like to hear about the 2 ways to setup multilanguage. Should I stay with Babel, that I know how to use, or should I give the new migxmultilang a chance? I find multilanguage always an intensive process in the development of a website, so it should be easy to implement AND to maintain. So what solution is the best?

Go for migxMultiLang. I've used Babel a few times, and am not at all happy with it. migxMultiLang is really nice; obvious and simple, easy to use. Just be careful to follow the installation and setup instructions exactly. Hopefully future versions will automate some of the process. In any case, it beats contexts and Babel.

Care to expand on the problems you've experienced with Babel Susan?

I think it's important to distinguish between multilingual and local sites here.

Steve

I don't like the principle of it. It's just a more complicated way of having a section in the Tree for each language, with Babel the duct tape and baling wire to hook things together.

migxMultiLang does it in a cleaner manner, with one resource and translations for that resource organized in one place. [ed. note: sottwell last edited this post 10 years, 3 months ago.]

We've been a longtime Babel-user and still use it in all our new projects. We checked the migxmutlilang addon but have some objections to use it. We made a pro's and con's list

Cons:
- There is no way to get unique URL prefixes for language-specific resources, eg: site.com/en/home, site.com/nl/home, site.com/de/home
- There is no way to get a seperate domain name for a language, eg: site.com/home, site.nl/home, site.de/home (there is a possibility with a dirty htaccess hack, but that's not really what we want)
- Can't use TV's
- Can't use Wayfinder or getResources
- We think an end-user will not experience it as logical
- You always have all languages for a page. There's no possibility to make one page language-specific. You have to use all languages, even if you don't want to

Pros:
- A clean resource tree

This led us to the the conclusion that we keep using Babel.

1. check http://languages.sottwell.modxcloud.com/fr/about.html, change languages, change pages. That's exactly what it does.

2. correct - so far .

3. Of course you can. Just add whatever fields or TVs you want to the MIGx configuration.

4. Above site uses pdoMenu http://translate.google.co.il/translate?hl=en&sl=ru&u=http://bezumkin.ru/modx/pdotools/snippets/2007/&prev=/search%3Fq%3DpdoMenu%26biw%3D1280%26bih%3D674

5. Having all the translations for a page right there while editing that page isn't logical?

6. You don't have to use all the languages. Any page that isn't translated defaults to the cultureKey language. And you don't have to use the multi-language templates for any pages you don't want to.

Quote from: sottwell at Jan 14, 2014, 11:58 AM

3. Of course you can. Just add whatever fields or TVs you want to the MIGx configuration.

or better to a renamed copy of the MIGX configuration, not that this configuration does get overwritten in case of upgrades.

Quote from: sottwell at Jan 14, 2014, 11:58 AM

5. Having all the translations for a page right there while editing that page isn't logical?

and with a little effort, the pages could be translated directly from frontend, isn't that what endusers like?

But I think everyone has to make his own experience. [ed. note: Bruno17 last edited this post 10 years, 3 months ago.]

I have almost completely switched over to pdoTools and its snippets for all of my listing needs.

Their description of pdoMenu says that caching of Wayfinder menus minimizes the speed advantages of pdoMenu over Wayfinder, but what about cases where you can't cache Wayfinder, like in the case of protected sites, where you don't want the menu visible to a logged-in user cached for everyone to see?

And - how do you translate and synchronize for example MIGX - items within Babel?

with migxMultiLang you can have:



inside mml_imageTpl:



just need to create MIGX-title - fields, for example: title_de title_en title_it
and translate them in one place.

Lingua anyone?