For instance, importing an XLF file may cause an exception due to the file imported not being in the expected format. To reproduce

• On demoauthor.magnolia-cms.com create a new page /travel/test with a standard template
• Add a textImage component to the main area and fill in with a title and a text
• Export as XLIFF
• Go to an online service http://xliff.brightec.co.uk/ and translate the file, then save the translation
• Reimport the XLIFF file just created
• An ArrayIndexOutOfBoundsException is thrown (see also screenshot). Nothing appears in the logs.

  ---

  The error seems happens when

• importing an XLIFF file not zipped.
  • Here our app could do some validation and check whether the file is in the accepted format
• importing an XLIFF file zipped but whose name does not reflect the locale code of the translation to be imported (e.g. de)
  • we could see if our import action could become more lenient in such a case, since the target language information is available in XLIFF file itself.

Finally we could possibly avoid asking users to choose an import format when the latter can be inferred from the uploaded file