i18n issue: "parent menu" settings should be a multilingual variable

Hi all,

I have the following situation:

1. I'm using superfish to render ONLY SECOND LEVEL menu items for main menu
2. It's a multilingual site, so I'm using i18n that's based on variable module to store multilingual variables

EXAMPLE:
my main menu:

Item1
--item1.1
----item1.1.1
----item1.1.2
--item1.2
Item2
--item2.1
---item2.1.1
---item2.1.2
--item2.2

So for the above, I have 2 superfish blocks:

1. superfish block 1 with "menu parent" setted to item1 -> renders item1.1 with its children, and item 1.2
2. superfish block 2 with "menu parent" setted to item2 -> renders item2.1 with its children, and item 2.2

All works very fine, but the issues start when I do the main menu translation in this way:
Translation mode for main menu: "Translate and Localize. Menu items with language will allow translations. Menu items without language will be localized."
I have some items that have to be localized, and some not. So for example main menu becomes:

Item1 -> Language neutral (I don't need localization for this item)
--item1.1 -> ENG translation
----item1.1.1 -> ENG translation
----item1.1.2 -> ENG translation
--item1.1 -> ITA translation
----item1.1.1 -> ITA translation
----item1.1.2 -> ITA translation
--item1.2 -> Language neutral
Item2 -> ENG translation
--item2.1 -> ENG translation
---item2.1.1 -> ENG translation
---item2.1.2 -> ENG translation
--item2.2 -> Language neutral
Item2 -> ITA translation
--item2.1 -> ITA translation
---item2.1.1 -> ITA translation
---item2.1.2 -> ITA translation

In the above, please notice that new translated items were added by i18n system (but I have to remake manually the hierarchy).

So the results:
For item1 tree all works fine, because item1 itself is not translated: superfish block 1 use item1 as "menu parent" and correctly shows:

if we are viewing ENG site version:
--item1.1 -> ENG translation
----item1.1.1 -> ENG translation
----item1.1.2 -> ENG translation
--item1.2 -> Language neutral

if we are viewing ITA site version:
--item1.1 -> ITA translation
----item1.1.1 -> ITA translation
----item1.1.2 -> ITA translation
--item1.2 -> Language neutral

The issue comes when I have first level item localized, as in item2 case:

if we are viewing ENG site version:
--item2.1 -> ENG translation
---item2.1.1 -> ENG translation
---item2.1.2 -> ENG translation
--item2.2 -> Language neutral

if we are viewing ITA site version:
inconsistent rendering: all menu items are shown

That's because superfish block 2 use item2 ENG as "menu parent" it doesn't automatically switch this setting to item2 (ITA).

If "parent menu" setting were a multilingual variable, I could assign item2 (ENG) for english and item2 (ITA) for italian

I'm not a programmer, but I think we need something similar to:

/**
* Implements hook_variable_info().
*/
function superfish_variable_info($options) {
  $variables['superfish_menu_[superfish_block_number]'] = array(
    'type' => 'multiple',
    'title' => t('Menu parent', array(), $options),
    'repeat' => array(
      'type' => 'select',
      ...
      ),
    'description' => t('Variable description', array(), $options),
    'required' => TRUE,
    'localize' => TRUE,
    'group' => 'Superfish',
  );
  return $variables;
}

/**
 * Implements hook_variable_group_info().
 */
function superfish_variable_group_info() {
 $groups['Superfish'] = array(
   'title' => t('Superfish'),
   'access' => 'administer site configuration',
 );
 return $groups;
}

/**
 * Implements hook_variable_type_info()
 */
function node_variable_type_info() {
 $type['superfish_block_number'] = array(
   ...
 );
 return $type;
}

And then retrieve the value with variable_get_value().

Please consider to add this feature, it will be useful to many.

Thank you very much