multilanguage and sylius

follow up of #703

@steffenbrem lets continue the discussion here, and keep #703 for the bug you found.

when we built the phpcr-odm multilanguage system, the main goal was that translations are transparent for your model and for the application using it. you set the locale on the document manager (e.g. in a request listener) and from then on all code can act as if there was no translations, and just "happen" to end up with the correct language. this turned out to be quite powerful while being really simple to use.

what exactly do you need? you can query the document manager to fetch all available locales of a document.

i would love to find a way so that sylius can use phpcr-odm multilanguage directly, rather than build a custom solution on top of it.

did you look at the "child" strategy for translation? then you get a specific node per language. maybe we could find a way to expose those better, for applications that want to work on multiple languages at the same time, if that is what sylius wants to do.

Start by reading issue #703 and the existing multilanguage behavior in the document manager, then examine the child translation strategy and how available locales are exposed. Compare these entry points with Sylius's need to work with multiple languages at once; done would require an agreed integration approach before implementation.

Written by the indexing model from the issue text.