* It should be logical that menu items identified as 'French' only appears when French is the selected language of the site, and the same for items identified as 'English' menu items. (As for now, both language are appearing in the menus).
* Also, since localizer is linking a node with its translations(ex: Node5 for english, Node79 for french, etc.), the menus should be providing the right node (Menu items cannot just be translated, they also need to point to the translated content which is in a different node). This is offered in SPIP, by example.

* Since they are many ways to generate menu items (via Administer>Menus , or via the 'Menu Setting' in the Node Edit form), any step-by-step guide existing for Localizer? The information provided with the Module doesn't indicate what is the correct way to translate the menus.

Thank you for your help! As bilinguism is required by our institution, the site can't be published until this is working correctly (and Drupal + Localizer can't be recommended for daily usage)

Comments

sylvain_a’s picture

By the way, i'm using a customized version of FOLIAGE theme. Some previous posts were suggesting the bug was linked to the use of nonstandards Theme. Actually, the bug repeats itself in every core theme.

Roberto Gerola’s picture

>It should be logical that menu items identified as 'French' only appears when French is the selected language of the site
No language is associated with a menu items.
Every menu items can have translations, and it appears in every language. This is how Drupal works.
If you need specific and different menus blocs for different languages, you can define different blocks
and make them visible only when the corresponding language is selected.

>the menus should be providing the right node
It is already so.

> The information provided with the Module doesn't indicate what is the correct way to translate the menus.
There is only one way, through the main menu edit interface.

>and Drupal + Localizer can't be recommended for daily usage
Do you think so ?
This is a partial list of websites that are using Drupal + Localizer : http://drupal.org/node/137248

Roberto

mcus21@drupal.cat’s picture

I had the same comprehension problem about menu localization and did not completely understand Roberto's comment either.
It's a little bit confusing when you try it for the first time...

You have to create a menu with several items, for the menu and for each item you can edit it again an select a language and press "change", then you can enter a new translated name and also a description for each item. The link is the same for all the languages and if is a node, localizer will show you the translated node.

It seems than in block configuration you can specify a language, but it does not work for menus.

Roberto Gerola’s picture

Example :

1. Create a page in English with the title : Hello - EN
2. Create a menu entry for this page with title : Hello , if you want assign an url alias to this page : en/hello
3. Click on tab translation and create the Italian translation : Hello - IT
If you want assign an url alias to this page : it/hello
4. Go under menu administration interface and select the menu item : Hello
5. Change the language with the top combo box to Italian
6. Translate the menu title to : Ciao

All the associations are made automatically by localizer.

sylvain_a’s picture

I'm back from vacation so i'm sorry for the delay in my answer.

I just wanted to say that it works correctly with your latest instructions.
Thank you very much for everything.

Roberto Gerola’s picture

Status: Active » Closed (fixed)
vikingew’s picture

Version: 5.x-1.9 » 5.x-1.x-dev
Component: Code » User interface
Status: Closed (fixed) » Fixed

Sorry for opening this one again but I had some problems to get this right due to the instructions here having a awkward ordering and they also left out one important step which is easy to fall on when new to the module. So I have done a new step by step instruction based on Robertos and set this issue back to fixed. That way it will become visible for 2 weeks until drupal automatically set it to closed again (which hides it from most searches).

Example :

  1. Create a page in English with the title : Hello - EN, if you want to assign an url alias to this page : en/hello
  2. Click on the tab Translation and create the Italian translation : Hello - IT, if you want to assign an url alias to this page : it/hello
  3. Now go to Administer->Site Building->menus
  4. Create a menu entry for english page with title : Hello , a description if you want and set Path: en/hello, chose a Parent Item (e.g. Primary links), set weight and Click Submit t create the menu
  5. Now select the new language with the top combo box e.g. Italian (don't click Change button yet)
  6. Change the Path to it/hello and click the Change button. This will gray (disable) Path, Parent item and Weight but it's ok.
  7. Now change Title to Caio, the description if you want AND click Submit. This final step creates the second translated menu.

One thing I noticed though and this is particullary annoying if you already has some (english) menus set from start. If you now go back to the Menus interface to edit/create more multilang menus, the language selector is still (in this case) Italian and Path, Parent and Weight are disabled, even if the menu is english from start.

I haven't tested yet to create a completely new item, but I suspect it will still start out from the last language changed to, which in such case must be a bug or?

Anonymous’s picture

Status: Fixed » Closed (fixed)