Hi David
I am lurking the documentation mailist to help pick aspects of the documentation process that may apply to the development of the TDF/Drupal Drupal site. I'm a member of the Drupal team.
However, I am also a member of the marketing team. If I could perhaps just add my opinion to this.
From the perspective of the "outside world" the public face of the LibO documents section, it would seem to make sense that documents be provided in the first place in our native ODT formats. This should be trumpeted as our success in document achievement. I think that this is an expectation that we all share.
Also, if we are going to keep advertising the virtues of the ODF files. It would seem to make sense that we find ways to make the ODF files system "play nice" with the internal document flow. What better occasion would we get than having the use of a corporate-like structure such as the "TDF/LibreOffice document team division" use the ODF files internally at developing documents from start to end. We have our devs on-side for the development of an Office Suite championing the use of ODF, would it not make sense that we would try to make the creation/editing of internal ODF documents part of the internal process? The devs could could help in making this work. We could then, without any doubt, suggest and prove that using the ODF in creating documents in a corporate structure, from start to end production, is entirely and assuredly possible.
If so, as a group of committed document editing professionals, as you all are, you could use this occasion to streamline the ODF documents to work in such a process.
This would certainly help in marketing our LibO Suite as a viable office suite for the corporate/enterprise world.
Just my thoughts.
Marc
Member of the TDF/LibO Marketing Team
Member of the TDF/LibO Drupal Website Development Team