You may have learnt that we've just released a new version of the ODF Translator yesterday, called 0.2-Final (even if it's not really a final version, as I've already explained on this blog), providing a lot of new features for the direct conversion (from ODT to DOCX) and a prototype of the reverse conversion (from DOCX to ODT). While the reverse conversion is only at its begining, the direct conversion now looks quite good and provides most of the features that we expect from a converter. A complete list of features is available on SourceForge. The main functionalities that are still to develop are:

  • digital signature
  • encryption
  • section protection
  • drop caps

along with several other small features. The roadmap for both direct and reverse conversion is also available for download on SourceForge.

This release has been intensively tested by our test teams from Dialogika and AztecSoft. Test scenarios are described here and here. But this time, we also wanted to have an overlook of how the converter was behaving with real-life files. To this purpose, Dialogika gathered more than 450 ODT files on the internet and here are the results:

  • 411 documents were converted, validated and opened successfully in Word
  • 10 documents were valid, but could not be opened in Word
  • 28 documents were invalid but could be opened in Word
  • 7 documents were invalid and could not be opened in Word

Of course, this does not show anything about the way the documents were actually rendered in Word! But anyway, the results were not as good as we might have expected, so we made some quick investigations to identify the issues that lead to those results. After a one-day exploration, most of them could be fixed, and we therefore decided to publish a "Hot Fix" for the 0.2-Final next week. It won't add any new feature, but will fix those file crashes.

During this "real life" tests, we noticed that all the files created with the online application "Google Docs" were not converted successfully. This was strange enough for us to look in detail at what was wrong. And we found out that Google Docs was simply not able to export to ODF. Actually, the file menu says "Save as OpenOffice" and not "Save as OpenDocument". The output file is an SXW file (the legacy format from previous versions of Star Office and with an ODT extension! I don't know if by doing this way the guys from Google wanted to make people think that they had implemented the ODF format, but that was a nice try! ;-) I guess that they are working hard to achieve the compatibility, but in the mean time our converter won't be able to open documents made with Google Docs - no need to complain, we have commited to handle OASIS OpenDocument format, not all the formats of the earth!