Currently the eZODF extension does not provide the ability for a user to select which language their odf import/replace operation should use.

At the moment language is determined by the default language for the siteaccess, and whilst this logic may work for front end editors, it does not assist in backend content management or import operations.

The only workaround for this at the moment is to create multiple administration siteaccesses in different languages to support the import process, which is less than elegant considering every other multi-language operation can be undertaken in a single siteaccess.

Steps to reproduce

Create an object with multiple translations and try to update the contents of both translations via an odf replace operation.