According to the OOo XML specification, p. 112, "in both text documents and
spreadsheets, the default document flow of an XML document reflects the current
state of a document. An XSLT stylesheet or any other application that doesn't
acknowledge change traking information, process all insertions into the
document, but doesn't process any deletions".

Well, if I save a document with changes into OOo native format and then use an
unzipping utility to look at content.xml, everything looks as described in the
documentation, i. e. insertions are present in the default document flow,
enclosed between <text:change-start> and <text:change-end> tags, while deletions
are stored separately, so that only their place in the body text is marked with
a <text:change> tag.

However, if I save the same document as FlatXML, in the resulting file *both*
insertions and deletions are present in the same text flow, marked with
<text:change-start> and <text:change-end>. Since that's FlatXML which is
processed by various custom filters, in particular XSLT stylesheets, it is clear
that the resulting file will always contain a mixture of insertions and
deletions (of course if they are present at all) rather than a text
corresponding to the current document state.

To make my explanation more clear, I'm attaching a sample document which has
insertion and deletions, and the same document, but saved as FlatXML. Note that
I used my own version of the FlatXML filter (that's why the document is
indented), but, of course, the version from OOo SDK will produce the same
result, since SAX parser always processes XML tags in the same order.

I'm unsure it is really a defect, but at least I'd like to know if there is a
resaon for such difference between Flat XML and content.xml.