Thanks to Dennis for his thoughts. They make sense to a newbie to this
field ( with 40 years of intermittent programming experience)
Dennis E. Hamilton wrote:
To my mind, a 'standard' document, say for archival purposes, should not
have any extraneous 'information'. Libre office can include private
information but other XML agents should gracefully ignore this. Likewise
Libre Office should gracefully accept documents which do not conform to
its private structure providing they conform to an Open Document
standard. Do we need a .odt checker?
Corruption could indeed be triggered by there being an inconsistency between META-INF/manifest.xml
and what is present in the package.
It is interesting if that is a complaint about Configurations/.../current.xml (usually a
zero-length useless component), which is private information from the producer that is not defined
by ODF and can't be meaningfully used by any software other than the producer. For the most part,
that material appears to be gratuitous and unnecessary.
If my understanding is correct we have an internally inconsistent
document (directory) given that it refers to files which do not exist.
Your reference to 'a tightening of consistency' strikes exactly the
right chord to my way of thinking.
For unsubscribe instructions e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy