Using FAPE on entity formatter option form causes issues on multilingual sites

On a multilingual site, the FAPE added to the field formatter options can lead to save the body field in the wrong language.

Actually I do not understand the reason to add FAPE form inside panopoly_magic_form_ctools_entity_field_content_type_formatter_options_alter(). I really do not like FAPE, but as far as I know, it is supposed to edit directly a field value on a pane.

So why include FAPE form on a the display formatter options (an administrative form that is not supposed to edit a field value)? I may missed something here, so please give me the full picture in this case.

Whatever, if we have several languages, when customizing the full page display on a specific entity basis, we have the body field edit element appearing on the pane form when editing the pane configuration.

As we have an entity context, the code below add the body edit element to the formatter form:

 if (!empty($form_state['entity'])) {
    // Add the field edit form.
    fape_field_edit_field_form($form, $form_state);

Even if I do not understand the purpose, we are forced to enter a value to the body field (required option is checked in the content type settings). This is very disturbing when we simply want to modify the field formatter...

But at the very end, the value is not stored in the correct language, but to the Undefined (UND) key.

What I suggest is simply to remove the FAPE inclusion on this pane configuration, because it has no sense for me.