Answer to your question is very difficult.
First, a good definition for changes is necessary. Please, note I’m not a developer and consequently my remarks come from observed usage.
Changes are differences from a reference state. The reference state is created when you enable Edit>Track Changes>Record. Everything which existed before this event is considered the original document. Everything you type after is considered a change and will be displayed with fancy colours and effects.
Consider now a paragraph move. The move operation is decomposed into two elementary ones:
- a delete operation of the source material
- an insert operation at the destination location
From an author point of view, it is legitimate to keep the change history in the moved block(s) of text, but …
From an editor point of view (peer reading or review), moving a paragraph is a change. And it is a very important change because it may disrupts the smoothness of discourse or even cause inconsistencies (such as early reference to a point supposed to have been defined before the argumentation).
The editor should be notified of the deletion (therefore, the whole block is shown as deleted and this overrides the previous history) and of the insertion (the text is brand new there; there was nothing before and therefore the whole text is shown as new without prior history).
Perhaps Edit>Track Changes>Manage could give you some insight about the change history but, unfortunately, there is no display of the change itself. You may try to add comment there with a right-click on one of the items and Edit Comment but this requires a strict discipline.
Personally, I don’t see how to “tag” (to inform Writer) a move operation so that it is handled specially. This special handling nevertheless prevents an external editor to be warned about the move (the change history would be kept with the exception of the move itself).
In case you submit a feature request, you need to carefully specify what you expect, how it integrates with the existing feature and, most important, why a move operation (supposing you know how to designate it as such and is different from the simple common deletion-insertion pair) should keep the original change history (in which use case it is important to ignore the fact the block was moved).
To show the community your question has been answered, click the ✓ next to the correct answer, and “upvote” by clicking on the ^ arrow of any helpful answers. These are the mechanisms for communicating the quality of the Q&A on this site. Thanks!
In case you need clarification, edit your question (not an answer) or comment the relevant answer.
