RE: [office-collab] Change within a change?

["Dennis E. Hamilton" <dennis.hamilton@acm.org>]

If you are going to make overlapping/nested changes, you might need to use different user accounts to do some of them to see whether that prevents coalescing or not.

Also, it is not clear what the actual change was to the first-changed document to make the second-changed document.  Can you report the actions as they were done, rather than showing the text as you think it is being tracked.  (It looks like the only second change was to replace the word "people" with "men" in the insert from the first changed version.)

If you did an accept all changes, of course the second change should be reflected.  It looks like a bug if it is not.

What software are you using?  Some of this might need to be handled on the ODF Interoperability and Conformance where test documents and scenarios can be filed and tested across multiple implementations.

 - Dennis

-----Original Message-----
From: office-collab@lists.oasis-open.org [mailto:office-collab@lists.oasis-open.org] On Behalf Of Patrick Durusau
Sent: Friday, May 18, 2012 05:46
To: office-collab@lists.oasis-open.org
Subject: [office-collab] Change within a change?

Greetings!

Just describing the behavior I observe in OpenOffice, it does not appear 
to capture a change within a change.

Thus:

Now is the time for all good men to come to the aid of their country. 
(original)

Start change tracking:

Now is the time for all <del>good men</del><insert>bad people</insert> 
to come to the aid of their country. (first change)

Save text. Change tracking still on.

Now is the time for all <del>good men</del><insert>bad men</insert> to 
come to the aid of their country. (second change)

The <del> and <insert> elements are for explanatory purposes and have no 
relationship to any proposed ODF markup.

Note that when changes are accepted or rejected, the change from people 
-> men is not captured by the application and one assumes by the markup.

Is that correct? As a description of application behavior?

Second question: Is that as it should be?

Thinking that in legal documents, for instance, or legislative 
documents, I would want to have multiple layers of changes and the 
ability to accept/reject or even skip levels. (Although skipping levels 
might create other issues. User beware.)

There are some legislative editor proposals that may have useful 
information about change tracking. Will try to run those to ground.

Hope everyone is looking forward to a great weekend!

Patrick

-- 
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
OASIS Technical Advisory Board (TAB) - member

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau


---------------------------------------------------------------------
To unsubscribe, e-mail: office-collab-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: office-collab-help@lists.oasis-open.org