Integration between i18n_menu and entity_translation.
#1182058: Add Entity Translation (entity_translation) support for menu items using Menu Translation adds support for entity translation (as in "don't touch it if it has ET"); the purpose of this module is to integrate menu translation into the ET translation workflow:
It adds a "menu translation" form to the entity translation form, so that users can translate menu items at the same time when adding/editing the translation of a node
- Both types of menu items are supported:
- If the menu item is language neutral, a string translation form is added (here is an early screenshot from the i18n issue)
- If the menu item of the source node has a language, then a "normal menu form" is added (which allows to create a new separate menu item for the translation)
- It ensures that the menu edit form matches the language of the node being edited (language neutral menu items would normally always show up in the site's default language)
Be aware that this will probably end up in the entity_translation module. See #1433630: Initial release of i18n Entity Translation? / Current status / What needs testing ...a.k.a. "Are we there yet?" for discussion+details.