FPP language issues

So basically the node module does nothing, but the Locale module does it for the node.

When locale is enabled, you can have multiple languages. If you edit a node type and enable multilingual on it, the form_alter kicks in on the nodes of that type and the language selector gets printed:

function locale_form_node_form_alter(&$form, &$form_state) {
  if (isset($form['#node']->type) && locale_multilingual_node_type($form['#node']->type)) {
    $form['language'] = array(
      '#type' => 'select',
      '#title' => t('Language'),
      '#default_value' => (isset($form['#node']->language) ? $form['#node']->language : ''),
      '#options' => array(LANGUAGE_NONE => t('Language neutral')) + locale_language_list('name'),
    );
  }
  // Node type without language selector: assign the default for new nodes
  elseif (!isset($form['#node']->nid)) {
    $default = language_default();
    $form['language'] = array(
      '#type' => 'value',
      '#value' => $default->language
    );
  }
  $form['#submit'][] = 'locale_field_node_form_submit';
}

I suppose we could replicate this by enabling multilingual on individual FPP bundles but this is up to you guys. It's not difficult either, we just need to add the same multilingual selector on the bundle edit form (admin/structure/fieldable-panels-panes/fieldable_panels_pane/edit) and save it to a variable (exactly like locale does for node types). Then we apply based on that either directly a language value or a selector. Let me know if you wanna do this. (Also keep in mind what locale_field_node_form_submit() does)

Based on my finding, I cleaned up a bit the language selector:

• Used the same technique as locale
• Realized we don't need a check for entity translation because if it's enabled it will just replace the language selector. I guess this is what happens to node as well.