As I mentioned in an earlier post, my favorite feature of Scrivener is the ability to differentiate the text the author sees from the text a reader sees. In that post, I described how to separate the two using the "Compile" mechanism, which allows you to control how entire subdocuments appear.
Today I want to go over the feature of Scrivener I use most frequently. It is the ability to separate author's text from reader's text on a sentence-by-sentence level. As before, it is best to follow along in the sample document included here.
0 Comments
One of the greatest benefits of Scrivener is the ability differentiate text the author sees from text the reader sees. In programs like Word and Pages, this can only be done by using the "comments" mechanism. Comments, however, can only naturally handle a subset of the kinds of texts an author may wish to hide, as discussed here. Scrivener is more sophisticated, without being more complicated.
There are several ways to distinguish Author's Text from Reader's Text in Scrivener. I'll begin with the least fine-grained way. Tools: Scrivener --> Compile Action and Options. Method: In Scrivener, what the reader ultimately sees is the result of Compile command. This command filters the author's text in a variety of ways and set the output format. Scrivener is worth every penny. In fact, it's the only piece of software I recommend students buy. Everything else can be done open-source. For this post, I'll merely list why I use Scrivener, and leave more detailed instructions for later posts.
|
Categories
All
Archives
October 2018
|