Radoslav Dejanović wrote:
> I believe that is the point - we do not want applications to do any
> internal modifications of a document unless the user adds, modifies or
> deletes something. Input file should be exactly the same as the output
> file if there were no user interactions (we should consider spell
> checking as user interaction).
So, basically:
"when an application doesn't support an elements or an attribute that is
part of the ODF namespaces (or any namespace ?), the application shall
not change or remove said element or attribute (unless the parent is
changed or removed ?)"
So if app X opens an ODT with tables and X doesn't support tables, that
would be OK as long as X isn't removing the tables when saving the
document to a file.
Best regards,
Bart
