Editing Translated Menus under Site building has redundant language

Yes.
I'm going to implement this proposal : http://drupal.org/node/111773
Read there the sense of this solution.

I already have started coding on the form-side of things for this, but don't have as much time as I want for it.
Hope to get a patch ready this weekend ... at least for the "edit menu item" and "edit menu" pages.

Ok.
So I'll can finish to fix some annoying bugs and perhaps starting with the integration of the
variable support.

This path for localizermenu.module does some form-magic, so we don't have too many input fields, and the current locale is always in the main-fields.
What probably missing, is to pre-set the default-value for the translation with the original version, if it doesn't exist yet.
I also didn't touch the database logic behind all this ... Roberto, you know that code a lot better than I do ;-)

Apply patch from inside the localizer-directory.

Fine for the UI-side of things, or something ugly?

Many thanks.

I'll integrate it during this weekend, and I'll apply a similar
system also for taxonomy support.

If you want help on the form-side somewhere just tell me, I think I've got a bit of a feeling for that now.
One little problem I've just seen with my patch: on the edit-menu-item page, the title and description fields have swapped place on the main form, that may need adjusting weights or adding the items in reversed order ...

This has been fixed in v1.7 and is optimized in v2.x.