Revision Mode Questions

Hi. Due to my bad writing [ :wink: ] I need to add more revisions then the five that are set up. Is there a way to add more revisions / colors. Failing that, is there a way to wipe all the revisions over the whole document easily so I can start again at the first revision?

thx!

Have windows version, can on dropdown choose remove colors. Could on major area do snapshot for revisions and compare as go forward

Thx GoalieDad. I need it more to track changes in the screenplay for the readers. So need a way to add more revisions or with one click, get rid of all revisions so I can start over. It seems you can only remove revisions in one document (scene) at a time.

In Scrivenings mode, too? :thinking:

Again can take endless snapshots of a document and give titles and use compare to see additions and deletions . To cut down on opening multiple file end all files with line of 3stars last line


Then merge multiple documents together and track changes for them at once with snapshots and can split at end if want will have original splits marked

Removing individual markings by level is easy to do:

  1. Load all of the text you want to strip the markings from in Scrivenings mode.
  2. Switch to the revision level you want to remove.
  3. With nothing selected in the text editor, use the Format ▸ Revision mode ▸ Remove Current Revision Color setting.

To answer your basic question though: there is no way to have more than five of them. There are however other tools that may help to essentially extend that. Snapshots are one, as has been suggested, and inline annotations can be really helpful as well. Consider that you can create an inline annotation at the top, explaining what the colours related to at that point in time, take a snapshot, and then delete the annotation. Now when you view that snapshot in the future, you have a handy “legend” at the top.

But even just using annotations more, as an editing feature, can be really useful. They can be set to any colour you want at all, so there is no cap on how many different “types” you can have. It is true though that they help track a different kind of editing. It’s not the faceless “track changes” approach, but rather the annotative approach to editing. “I did this here”, rather than having what you did without any comment as to why.

Then merge multiple documents together and track changes for them at once with snapshots and can split at end if want will have original splits marked

A word of warning on that technique: unless you barely use the inspector that may be more trouble than it is worth. Anyone tracking status levels per section, using keywords, bookmarks, inspector notes, synopsis cards or other features will find splitting and merging to be a bit ‘destructive’.

1 Like

Couldn’t one use a random color of his choosing for revision 6 and +, then use image ?

Using say “revision 5” as a non permanent color.

image

image

You could virtually do as many revisions as you’d like.

Of course, one probably ought to weigh the value of maintaining color-coded visibility of increasing iterations of revision. Think of the poor script readers!

Hopefully as revisions go along one is settling some things, so previous revision stages should at some point be considered base text.

gr

((Ignorable part: Might be interesting if there was a command to decrement the revision level of all revision marked text. That way, you could always make one more revision level available. If it was like that, I think I would always start with the last revision level right away, so my latest revisions were always the same color, and the just previous revisions always the same color. Just talking in the breeze here.))

Yes. That point will be different for each project, but I think it’s helpful to remember that a revision history serves (at least) two potential functions. It can allow the author to experiment with different versions of the text, and it can support a complete timeline of the document’s history. The two functions are similar, but not the same, and the kinds of tools that support one may not be suitable for the other.

For instance, one of the purported advantages of Google Docs for collaboration is that every single change by every single collaborator is tracked. Which in certain legal contexts is very important. As a writer attempting to pull together a coherent text that third parties will read, though, I have no need or desire to see any of that. Let me evaluate the current base text (with comments) on its own merits.

In the Scrivener context, periodically creating a backup and purging the revision history allows you to establish a new base text.

1 Like