https://bugs.documentfoundation.org/show_bug.cgi?id=166723
--- Comment #26 from Lars Jødal <l...@rn.dk> --- (In reply to Eyal Rozenberg from comment #24) > (In reply to Lars Jødal from comment #23) > > In which way is the action an acceptance? The action of "Reinstate" (as it > > is still called) is to reject a change made by someone else > > Again, no. When you reject a change, the non-tracked document (the baseline > if you will), does not change. > > When you accept a change, the non-tracked document (the baseline) does > change. And this is indeed what happens with "reinstate". Maybe we use words differently. Here comes an example to talk from. To keep things simple here in ASCII, the example considers only insertion of text followed by Reinstate, not deletion of text followed by Reinstate Example: baseline: "Hello World" baseline + tracked change: "Hello, this is a great World" (change-tracking shows ", this is a great" as inserted text) Accept: "Hello, this is a great World" = changed baseline (the change is no longer tracked) Reject: "Hello World" = baseline Reinstate: "Hello[, this is a great] World" = baseline + tracked rejection (text in [] appears as deleted text) Reinstate + Accept: "Hello World" = baseline (End of example) I agree that Reinstate alone does not return the text to the baseline. But I do not agree that it is comparable to accept. There is a track showing what was suggested - but NOT accepted - as a change. Thus, the only change to the baseline is a track-change. If the track-change is accepted, we are back to baseline. (For deleted text, Reinstate will show double track-change: the text as deleted and as inserted. Again, the combined effect is to go back to baseline: Reinstate + Accept = baseline) Therefore, the term "Reject but track" still seems to me to describe the effect of the "Reinstate" function - but the term is of course only a good choice if others can agree. -- You are receiving this mail because: You are the assignee for the bug.
