Currently running version 1.1 of the i18n module and version 1.0-rc2 of the Translation Table Module and version 6 of Drupal.

We have a site that runs in both English (default) and Chinese. All of our menus (all created using the core menu system) show up as translatable in the Translation Table admin section, but when we input the translations and save them they are not reflected on the Chinese side of the site.

I've managed to manually get all the menu items translated (by creating a second set of language-specific menu items under each menu, which I didn't think was the way this was supposed to work), but the menu titles can't be translated without creating a whole new, duplicate, menu (which I'd like to avoid, and thought was possible via string translations).

Regardless of the underlying workings, if the Translation Table is showing the items and menus as translated, I suspect there's something wrong if that's not reflected in the user-side of the site.

Comments

Pasqualle’s picture

Title: Translations Not Passing Through to Interface » How menu translation works
Category: bug » support
Priority: Critical » Normal

There are more options in Drupal how to translate a menu. The menu translation functionality of this module is only useful when you use the i18nmenu module.

1. The easiest way (as I see and most like) is to create whole new menus for every language and only show the menu in given language.
2. Set the node language and on page admin/settings/language/i18n set "Content selection mode" to: "Current language and language neutral." This will guarantee that every menu item which links to a node in different language will be hidden.
3. Use i18nmenu. (note: 1 and 2 does not require i18nmenu)

In 1 and 2 you are creating a new menu item for every language, so you do not need the menu translation functionality of this module, as those menu items will not be displayed in other languages.
Honestly, I do not use the menu translation functionality either. I do the menu translation with the mix of options 1 and 2, it is much more intuitive.

dddave’s picture

What I noticed is that when I create a new menu item manually and set its language to a language not being the default system language translation table ignores that and assumes that the item is in the default language.
e.g.: I create a german menu item and my system has english as default language. Going to translation table to translate the item only allows tranlation into german. The "original text" is automatically assumed to be in the default language.

Pasqualle’s picture

@dddave: yes, that's right. That is how user defined string translation works (with i18nstrings module). The menu item language has no connection with menu item translation.

http://drupal.org/node/313293

The source strings to be translated must be defined first using the site's default language ...

dddave’s picture

Uff. I am working with i18n quite a while now and mostly I get it right. Nevertheless this stuff is a real skullcracker sometimes. ;)

Thanks for taking over this module which becomes very useful.

Pasqualle’s picture

Status: Active » Fixed

I guess this issue is fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.