I don’t think that revision mode allows that. You’ll have to use the comparison feature for snapshots ; comparing a snapshot of your text from before with one of what your collaborator sent you back.
It’ll show you in red (and strike-through) what was deleted, and in blue (+ underlined) what was added. Unmodified text in plain black.
You can even copy/paste the comparison’s result to a document if you wish, the colors and strike-through etc. will follow.
Revision mode doesn’t retain deletions. From the Scriv manual, section 18.6:
Limitations
Revision levels are not to be considered equivalent to “track changes”, as
seen in version controlled software, or Microsoft Word. They are very
simple, low bandwidth tools, that only mark modified or new text. Removed
text will not be marked in any way. If you wish to track all changes
between a document and its revised state, take a look at the snapshot feature
(section 15.8).
Next time, instead of actually deleting the text, have your editor use strikethrough to indicate deletion.
To add to the above, when revision mode is enabled, overstrike on text will use the correct colour, and will be found when stepping through revision markings.
Struck-through text isn’t deleted, but there is a compile option to strip them out, and a command in Edit ▸ Text Tidying to delete struck-through text in the editor.
One point of optimisation to the list, if you are mainly looking at one revision cycle here, then you should only need to create one snapshot, to record the text in the state you left it in, paste in your editor’s work and that’s all you need. If you select that one snapshot by itself and click the Compare button it compares with the current text in the editor.
Thank you. I have files nested in files. (heading level 1, heading level 2, etc.). When I click on a different file, the snapshot does not appear there. That is why I wrote to create a new baseline snapshot for each file. Am I doing something wrong?