Menu Views and locale/translation module with path prefix

Hello

we're having some difficulties with Menu Views used together with the core Locale module and Content Translation module.

whenever we have more than one language active, using path prefix detection (ie, /en, /pt, /fr, etc), and we navigate to the menu being utilized as a Menu Views, something weird happens...

the menu view does load, the content being clicked does load too... but the menu collapses and no items listed bellow it, nor are even processed by drupal (no html, nothing).

explaining further,
we would have, for example, 2 languages - english and portuguese.
for these, we would have contents with their respective translations.

the paths (being generated with pathauto or custom made) would look like this:
current exhibits
/exhibits/current/number2 (content #2 in default language, ie, portuguese)
/en/exhibits/current/number2 (content #2 english translation)
/pt/exhibits/current/number2 (content #2 portuguese translation)
archived exhibits
/exhibits/archive/number1 (content #1 in default language, ie, portuguese)
/en/exhibits/archive/number1 (content #1 english translation)
/pt/exhibits/archive/number1 (content #1 portuguese translation)
etc

where each path (/exhibits/current and /exhibits/archive) links to different views/variants of the same view (filter by date in date field).

the menus would be built like this:
Exhibits (simple menu)
» Current (menu views attached)
» Archive (menu views attached)

all this would work fine _until_ you enable more than one language.
now, with more than one language enabled, when you hit a content link from the menu view (ie, Exhibits » Current » number 1), as the paths are being rebuilt internaly, somehow, perhaps, menu views misses something between the lines and doesn't catches the correct path, resulting in two things:
- the content does load
- the menu childs, active trails, etc, vanishes, displaying only the topmost root menu only (Exhibits)

is this a bug, a missing feature, or we are doing something wrong?

likely, it won't happen with domain based or other language autodetection methods.