Core

We experience problems with IRRE and translated records used in extbase/fluid.

1. An extbase extension brings it's own records. These records contain an IRRE field.
2. A plugin uses Extbase and Fluid to display the record data.
3. Such a record is created, two IRRE records attached inline.
4. This record gets translated.

Usecase 1 (works):

1. no further action

Result:
Two IRRE records show up in the translated frontend.

Usecase 2 (works):

1. The IRRE records are localized via the "Localize all records" button.

Result:
Two translated IRRE records show up in the translated frontend.

Usecase 3 (does not work):

1. The IRRE records are localized via the "Localize all records" button.
2. A new IRRE record is attached to the localized record.

Should:
Three IRRE records should show up in the translated frontend. (no localization parent is set)

Current state:
Two IRRE record show up in the translated frontend. The newly created one is missing, even though visible in the backend.

Usecase 4 (does not work):

1. The records are localized via the "Localize all records" button.
2. One IRRE record is removed from the localized record.

Should:
One IRRE record should show up in the translated frontend.

Current state:
In strict mode it's fine, only one IRRE record shows up in the translated frontend.
In fallback mode, one localized record shows up even and one IRRE record of the default language even though only one record is visible in the backend.

Usecase 5 (does not work):

1. The records are localized via the "Localize all records" button.
2. The records are removed and two new ones are attached.

Should:
Two IRRE record should show up in the translated frontend.

Current state:
In strict mode zero IRRE records show up in the translated frontend.
In fallback mode, two IRRE records of the default language show up even though not visible in the backend.

You can use the attached example extension to reproduce the behaviour. I included a t3d with the described setup as well.
Languages 0 and 1 are assumed.