Object names based on values from objectrelations attributes are either non affected or wrongly set by translations of these attributes.

Using related objects' attribute values to name objects cause some odd results in multilingual setups.

Steps to reproduce

On an eZ Publish 4.4 with two languages (for instance: English as default and Portuguese).
. Create an ingredient class with the following attribute(s):
. Name: "name". Type: "text line"
Set object name pattern to "<name>"

. Create and ingredient_line class with the following attribute(s):
. Name: "qty". Type: "integer"
. Name: "ingredient". Type: "object relations". Picking values from "ingredient" class
Set object name pattern to "<qty> <ingredient>"

. Create an object of type ingredient in Eng: Sugar. Translate it to Por: Açucar
. Create an object of type ingredient in Por: Leite. Translate it to Eng: Milk
. Create an object of type ingredient in Por: Café. (don't translate it)

. Create an object of type ingredient_line in Eng.
Type "1" into "Qty".
Available ingredients to pick in Object Relations field: "Sugar", "Milk", "Café".
Depending of your choice the new object will be named "1 Sugar", "1 Leite" or "1 Café"

. Create an object of type ingredient_line in Por.
Type "2" into "Qty".
Available ingredients to pick in Object Relations field: "Sugar", "Milk", "Café".
Depending of your choice the new object will be named "2 Sugar", "2 Leite" or "2 Café"

Conclusions:
. Object relations pick box ignores translation of objects (shows default site language versions whenever this exists)
. Naming templates seems to pick the original version of object related objects to form the name of a parent object.