improve workflow for multi-lingual site My client is having a terrible time managing multi-lingual content in drupal 7.  I'm using the internationalization module and drupal 7's default capabilities in managing multiple languages.  Here's an example workflow my client executes, with bold statements that indicate challenges.


Client begins to add new content of content type page.  He fills out title and selects language as English.
Client clicks on menu settings, and select Provide a menu link.  Under Parent item, client selects from the drop down tree About.
Client publishes the page.
Client clicks on Translate to translate the page.
Client clicks on add translation for French to see the add content page.
Client notices all the fields except menu settings is populated.  This irritates the client.   Client expects the CMS to know that the A Propos menu link is the french equivalent for About menu link, and to have populated accordingly.  But instead, client must go through hundreds of link.


Here's another example workflow that illustrates a big problem.


Client wants to re-structure the site map.
Client goes to an ENGLISH page in the CMS, goes to menu settings, and changes the Parent item to the Home menu link.
Client presses Save.
Client goes to FRENCH version of the same page.  Client needs to repeat the process of Parent item but find Accuiel menu link.  This irritates the client because client expects the CMS to be smart enough to know Accuiel menu link is the french version of Home menu link, and when the English page was moved from About to Home, then the French page should have moved from A Propos to Accuiel.


As it stands now, the client feels like he's managing two websites individually.  Can anyone suggest a workflow that can reduce the client's workload by about half ?  Simply having drupal reflect site map changes in english into french would reduce workload by about half.
As far as I can tell this is a problem, the menu items aren't connected so the only thing that links them is through the node they are connected to and their translation sets.

Another possibility, but I never used it like this, is to make the menu items translatable and there's a module inside i18n that redirect links to the right language.