https://bugs.documentfoundation.org/show_bug.cgi?id=166723
--- Comment #43 from Telesto <[email protected]> --- (In reply to Eyal Rozenberg from comment #42) > (In reply to Telesto from comment #40) > > A) Bob inserts XYZ. Alice opposes (mental state), but wants to keep it for > > further discussion. > > > > Manual steps: Alice accepts the change. Turns track changes ON. Deleted the > > insertion from Bob > > > > Essence: Opposing against insertion implies rejection. So reject insertion, > > but keep. It's not a full fledged rejection (yet). Baseline is changed. > > This scenario is one where "reinstate" would _not_ be used. That is because > if Alice opposed the change, she would not introduce it into the baseline > document. Introduction into the baseline document means that if there is no > agreement on further changes - the change is final. So, in your example, > Alice would either Reject (if she has the authority); or keep Bob's change > as tracked, making a comment perhaps. I) I might have misused phrase baseline II) Do you mean that case C 4 (below) shouldn't be used or exist in a proper workflow. Instead a comment should be made? Example borrowed from comment 26 A) baseline: "Hello World" B) Insertion by BOB: ", this is a great" with track changes ON. Result: "Hello, this is a great World" (change-tracking shows ", this is a great" as inserted text) C) Options for Alice 1) Accept: "Hello, this is a great World" = changed baseline (the change is no longer tracked) 2) Reject: "Hello World" = baseline 3) Do nothing; Nor accept; nor reject 4) Reinstate: "Hello[, this is a great] World" = baseline + tracked rejection by Alice (text in [] appears as deleted text). -- You are receiving this mail because: You are the assignee for the bug.
