I created a couple of multilingual sites with Drupal 4 + i18n module, then with Drupal 5 + Localizer module, and I hoped that Drupal 6 would support all multilanguage needs in the core, without any extra modules and patches.

With core/optional Locale and Content translation modules, I'm able to create nodes in different languages, and switch between them. However, at this point I fail to understand how to make viewable on the front page only items in the relevant language? (I see them all, despite switching between languages).
How to switch language for site title, blocks, menus, an so on? Create conditions based on URL language prefix or language-related PHP variables?
Am I missing something, or functionality of the Drupal 6 core localization modules is currently indeed much inferior to that of Localizer or i18n (and just inadequate to create a normal multilingual site)?
And what to do? Improve the core, or port these modules to D6?

Comments

jjalocha’s picture

Category:bug» feature

2008-02-24 EDIT: Moved my issues to separate reports (http://drupal.org/node/226062 and http://drupal.org/node/226065).

jjalocha’s picture

Category:feature» bug

Sadly, this issue makes the whole content translation quite useless, thus marking it as a bug. I hope we get some attention here, thanks.

GN’s picture

Category:feature» bug

The good thing is that i18n is already awailable as 6.x-1.x-dev - and it works, so that it's already possible to do multilingual sites with D6 + i18n. Another good thing is that now it's possible to do multilingual sites with language-symmetrical URL's - e.g. "en/contacts" and "fr/contacts" (which did not work for D5 + i18n nor for D5 + Localizer v.3 because of identical path aliases for different nodes not being allowed; it worked for D5 + Localizer v.1 with manual inclusion of lang prefixes in path aliases).

What I wonder about is why development of multilang support included in D6 core stopped just one step short of being adequate for creating a normal multilingual site without any need for external modules.

jjalocha’s picture

Thank you very much for the i18n suggestion, I'll definitely try this! But I still doubt that language-symmetrical URL's really work, because of Bug #226062, ie, the path prefix for the default language never gets applied for me.

matbintang’s picture

Had the same issue. I found a work-around by un-selecting the "Publish" option on the translated page.

GN’s picture

And does the translated version show up were appropriate after this trick?

Gábor Hojtsy’s picture

Status:Active» Closed (works as designed)

Drupal 6 includes some multilanguage features, but content/user/comment listings, menus, taxonomies, site settings (like site name, mission etc), blocks, user profile details, and so on all require contributed modules to translate. For listings, you can easily use Views module for the others i18n for Drupal 6 is already working, Localizer is not even started, so that will only be an option later.

GN’s picture

Thank you for the explanation Gábor (and for your valuable contribution, too).
I agree that Drupal 6 is a big step forward in terms of multilanguage support, though I probably misunderstood the announcements and somehow expected it to do this without any need for external modules.
For example, I like in D6 its support for language-symmetrical URLs (e.g. "en/about" and "fr/about") - it was not possible in D5 + i18n because of the system not allowing duplicate path aliases.
(Actually, it was possible with D5 + Localizer v.1 if adding the language prefix to the URL manually - but not for Localizer v.3 once it started adding the language prefix automatically).
This is VERY important if you want to switch a site to Drupal and need to preserve the existing language-symmetrical URLs.

Alan Oliveira’s picture

sounds poor but

create a new type of content called: Block Title

create 3 nodes (example)
* Ola Mundo (portuguese)
* Hello World (english)
* Hola Mundo! (spanish)

create 1 view and Filter it by Node Language, add a Block display and put it above the other block

so it name will change when the user click on the flag..

its a visual trick but should work fine

GN’s picture

Yes, I think it should work fine, but I guess there should be simpler ways to do things like that.
E.g. with i18n multilngual blocks, or perhaps with the Language section module (http://drupal.org/project/language_sections).