Multilingual Content Management Systems?

Azraael asks: "I need to make a website for a small business. The website must be available in several different languages and allow for easy switching between the different versions (with little flags in each page that has multiple versions, or some scheme of the sort). User logins are not required. I was thinking of using a CMS to accomplish this in an efficient and easily extensible (more languages, more pages, etc) way. What would be the best option? I've tried Wordpress but it seems to lack multilingual support of the type I described, while having too much of a weblog feel. Mambo with Mambel seems spotty at best. Has anyone on Slashdot done this before?"

Comments

Just write it?

[biryokumaru]

Um, why don't you just write it? Do you not have the hour or two it would take to write and debug a simple, CMS based website? I mean, WordPress? Come on!

Of course, it might just be my perception that it only takes an hour or two... you know what happens to time when you code, even when it's just web design.

Anywho, you could always just use a wiki without the whole user-added content stuff if you're really lazy.

Re:Just write it?

[Bogtha]

Um, why don't you just write it?

"Spending an hour or two" writing a CMS is not going to result in a very good CMS. Will it have a GUI for updating pages? Does it handle caching well? What about granular permissions, where somebody in one department can edit their subsection but not another subsection? And so on... there are a lot of little things that you forget about when saying "it'll only take a few hours" that mature CMSs do that your quick hack won't.

you know what happens to time when you code, even when it's just web design.

"Just" web design is pretty difficult. You have to cope with severe deficiencies in multiple browsers, memorise weird, counter-intuitive hacks to get things working in Internet Explorer, code three different ways depending on what features are available, remember to avoid some parts of the specification because they are unreliable, and remember to do the complete opposite of what the specification says in other instances because nobody bothers reading it, and so on.

I know it's trendy to think of web developers as lesser beings than "real" programmers, but we've got to put up with a hell of a lot of crap. Jeremy Zawodny (the Yahoo/MySQL guy) blogged about this: Respect for Web Developers - read the comments for a bit of insight.

plone.org

[uits]

http://www.plone.org/

Re:plone.org

[byolinux]

Plone 2.1 contains multi-lingual support by default - LinguaPlone. Works really well. /me is at the Plone conference

Lenya supports mutiple languages

[JumpSuit Boy]

Each page can have different language versions that are shown based on what the browser requests.

Have you checked out MediaWiki?

[mellon]

http://www.mediawiki.org/

This should let you do your text in whatever language you want, although you might find yourself wanting to tweak the style sheet.

Don't use flags to indicate language

[Bogtha]

A tangent, I know, but you shouldn't use flags to denote languages. To use the most obvious example, which flag are you going to use for English? The USA flag? Congratulations, you've pissed off all the Brits. The Union Jack? Congratulations, most Americans won't even recognise it, not to mention the fact that's the flag for the UK (it's not the English flag). What about the Canadians? And the Australians?

Jukka Korpela has written an informative article about this.

Re:Don't use flags to indicate language

[fodi]

I think this depends on what the flags represent. If the flags represent the nationality of the people its aimed at, you have a valid point. i.e. if you were serving different content based on nationality or geographic location.

If, however, the flags represent mere copies of the same site in different languages I think it's less of an issue. Americans, Australians, etc still speak English. French-Canadians, French(wo)man, Nuemeans (spelling??) still speak French...

Re:Don't use flags to indicate language

[treerex]

If, however, the flags represent mere copies of the same site in different languages I think it's less of an issue. Americans, Australians, etc still speak English. French-Canadians, French(wo)man, Nuemeans (spelling??) still speak French...

The English example isn't a good one: use the US flag and most everyone will know what languge you mean, though you still run the risk of alienating other non-American English speakers and the risk of further American imperialism. ;-)

A bigger issue is Chinese: do you use the PRC flag for this? Congrats, you just seriously annoyed people in Taiwan. Use the Taiwanese flag? Good job, you've just incurred the wrath of the PRC Government. Hong Kong's flag? Confusing: now you're using the flag of a "special administrative region" of the PRC, but one that speaks Cantonese: are you including Cantonese characters in your site's localization (and, by extension, using the HKSCS character set?)

The answer here is simple: don't use flags as an indicator of language. Instead use the name of the language in that language. Localizing for Finnish? Use "Suomi". Japanese? Use the kanji for nihonjo.

The only time where it is arguably OK to use flags, is when you are using them to represent the country itself: if you have separate sites for the UK and the US, you can use the Union Jack and the Stars and Stripes: iTunes Music Store does this, for example.

How about looking around first?

[Korgan]

Start with http://www.opensourcecms.com/ and have a look at all the various packages listed there. They don't list all available programs, but what they do list are demonstrated there as well.

All packages are required to be coded in PHP, however if you want to start looking at other languages (like perl or ASP) then I suggest looking at HotScripts.com and checking out whats listed in the lists there.

Failing those, how about a google search for multi-lingual CMS packages?

Re:How about looking around first?

[GrumpySimon]

CMSMatrix.org is another place to go - it doesn't limit the CMSes to PHP/MySQL ones, and allows you to narrow down the list by your required features. Very useful.

Once you've got a shortlist, then drop by opensourcecms, or the website for the actual app, and try out their demo.

--Simon

Plone

[Earlybird]

Plone does exactly this -- it's one of its main features. Plone probably has the best interionalization/localization support of any current CMS.

Take a look at phpWebSite

[RedLeg]

phpWebSite looks like it has the features you're looking for, plus it:

• Has a nice license (GPL / LGPL)
  
• Is actively maintained by someone with a budget (Appalachian State University), who also actively uses the package, so it's not likely to be abandoned, go stagnant or have unpatched security issues
  
• Supports multiple languages
  

Hope this helps....

Red

ezPublish

[elkyle]

http://ez.no/

Although the name may sound like it is a wimpy CMS, ezPublish is one of the most impressive CMS's around. I am currently in the process of adopting it as the base for my employer's website redesign.

Yes, it is wrote by Norwegians, but their English is superior to that of many native speakers. Also, they have an amazing model for translations and versioning (keeps the 10 most recent versions of a document by default). It also has a nifty nodular system of organizing pages.

At first, it seems a little confusing, especially when the manual starts talking about nodes and objects and IDs and whatnot, but it eventually makes sense. Once that happens, you have a great deal of creative abilities, with templates and the such. I shied away from many other CMSs because they assumed (or at least appeared to assume that) you wanted to do one certain thing, and God help you if you wanted to do something else. ezPublish really seems flexible.

Oh, and to the "CMSs only take an hour or so" group: I wrote a CMS working with one other person, and we easily put 500 man-hours into developing it, adding custom functionalities, and making it look acceptable to non-technical folks (we still don't have a graphical interface, just HTML menus and tables with a sprinkling of Javascript).

Kyle

TextPattern

[e271828]

Textpattern may be what you are looking for. Although it is used for blogs, it is very easy to setup as a general purpose CMS. And it seems to have good unicode support for your multilingual needs.

Accept-Language

[molo]

Whatever your solution, make sure it supports the Accept-Language: HTTP 1.1 header. See RFC 2616, section 14.4.

Example:

Accept-Language: da, en-gb;q=0.8, en;q=0.7

would mean: "I prefer Danish, but will accept British English and other types of English."

-molo

Drupal

[remikun]

I've been using Drupal since a while now. When I need a "community" or "journal" Web site, I use Drupal. (Don't say 'blog', please... Please don't. I hate the word.) A few of my sites are multilingual, hence I use the i18n module available on their site. It does require you to modify a few little things in the initial database and to apply patches on the source code, but it works. Also, after applying the patches, not only can you put links to switch languages, but also the URLs are simple: /en/ for English, /fr/ for French, etc. Plus, Drupal has a good API. That's why I like it so much.

Try Red Dot

[TripleE78]

Unfortunately, it's neither free as in beer nor as in speech, and requires IE[0], but Red Dot is what my Corporate Masters have me using on a daily basis.

I haven't had to use language support a lot, but it seems fairly solid. It does help that it's a German company that markets to Europe, the US, and others. Language support is sort of a given.

~EEE~

[0] I think I just described the Trifecta of Evil for Slashdot. :(

xaraya

[an_mo]

Xaraya is a highly extensible and customizable system. You may want to give it a look.