In our workflow we use one menu per language. This quickly becomes cumbersome. I've started developing a module to be able to set a language per menu. Dropdowns where one can choose a parent item are also filtered by this language, only leaving menus that are language neutral or have the current languagee. What's left to do is override the menu overview page to be able to filter the menus per language.

This issue is see if this should be integrated into the i18n module or if I go and create separate project.

CommentFileSizeAuthor
#10 i18n_menu-1039152-10.patch1.67 KBfloretan
#4 i18nmenus.tar_.gz1.97 KBjax
#4 i18nmenus.png102.64 KBjax
#4 i18nmenus.tar_.gz1.97 KBjax
i18nmenus.tar_.gz1.57 KBjax

Comments

jose reyero’s picture

jose reyero commented

This looks really interesting. It will be welcomed as a patch for i18nmenu.

Actually, I think I am adding this feature into D7 version.

jax’s picture

jax commented

I would prefer to not integrate this in i18nmenu since enabling i18nmenu enables languages per menu item. I think this should be a separate module since I don't want the functionality in i18nmenu.

If it has to be integrated into i18nmenu we need an option to be able to choose which functionality should be enabled.

jose reyero’s picture

jose reyero commented
Version: 6.x-1.x-dev » 7.x-1.x-dev

Fine, also I wouldn't be that interested on new features for 6.x

But about 7.x, I think it would be something good to add, your feedback will be welcomed here.

I'm thinking about having some options for menus (like for taxonomies).

jax’s picture

jax commented
StatusFileSize
new i18nmenus.tar_.gz1.97 KB
new i18nmenus.png102.64 KB
new i18nmenus.tar_.gz1.97 KB

Here's a completely functional version for Drupal 6. I've got an almost functional version for D7 as well but that one won't be completed until next week.

Here's an image of the menu overview screen.

jax’s picture

jax commented

I see that you have added something somewhat similar in the D7 module: "Fixed Language. Items will have a global language and they will only show up for pages in that language.".

I've also continued work on a D7 version and will put it here this weekend. I'll try to merge some features into i18n.module then.

jose reyero’s picture

jose reyero commented

Yes, for D7 you can "translate menu items", i.e. create translation relationships between menu items.

Menus/Menu items work now pretty much like Taxonomy/taxonomy terms.

The only thing missing is getting these translations work for language switcher links.

steinmb’s picture

steinmb commented

@Jose Reyero thanx for all your hard work with this module.
Regarding the translate menu items, is it implemented in the latest dev. version? I'm able to create translated menu items, but switching language does not reflect any changes in the related menu block. All the items in the menu is still displayed.

skilip’s picture

skilip commented

It would be great when the configuration AND translation of menu (items) is equal to taxonomy (terms) from a UX point of view. Like in l18n_taxonomy you could choose the following options:

  • None. No multilingual options for this vocabulary.
  • Localize terms. Terms are common for all languages, but their name and description may be localized.
  • Per language terms. Different terms will be allowed for each language and they can be translated.
  • Set language to vocabulary. The vocabulary will have a global language and it will only show up for pages in that language.

Couldn't i18n_menu have the same configuration settings?

steinmb’s picture

steinmb commented

+1 from me that we unify the UX.

floretan’s picture

floretan commented
StatusFileSize
new i18n_menu-1039152-10.patch1.67 KB

Menus with fixed language are only hidden correctly when used as built-in menus, but not when used as menu blocks. Attached patch adds a test for that.

floretan’s picture

floretan commented

Moved the menu block problem to a different issue (#1156502: Hide menus with fixed language when used as blocks.) to avoid interfering with the UX discussion here.

jose reyero’s picture

jose reyero commented
Status: Active » Closed (won't fix)

The main issue's patch is not up to date with i18n for d7. About menu options, there's a difference between menus and taxonomy and it is that menu items can be moved around from one menu to another so it seems more practical to have both options (localize/translate) merged for menu items.

troyer’s picture

troyer commented

Jax, is there still any activity on this project?

jax’s picture

jax commented

No, we've not continued work on this. The current version of i18n already allows to set a language per menu so it wouldn't be much more work to modify the overview page to be able to filter per language.

richsky’s picture

richsky commented

I would love to see the filter for translated menu items on the overview page. It would be a nice UX improvement. Can you pass the starting code for D7?