Another thread reminded me–§25.3.2 under Structure and Content Table says “In the columns to the left of each type you will find a checkbox for each content element that can be optionally included by the compiler.” The boxes are to the right.
§26.1 says “The structure of folders created on disk will reflect their structure in the binder, so in this way you can export all of your files from Scrivener for use in another application if you so wish.” I wonder if it’s worth pointing out that the file are going to be sorted alphabetically in Finder, so not necessarily ordered as they are in Binder? Maybe irrelevant; I only saw it come up as a question once, because of the ability to use file numbering when syncing. Just wanted to mention it.
Thanks. Fixed the typo. On the second one, it does say reflect, which is always an inaccurate depiction of the original. But yes, that’s probably not a bad idea. Another thing that is probably worth mentioning is that any folder text will be in a file beneath the folder, since Finder doesn’t support folders with text. Added that too.
True enough! I just figured the manual wasn’t long enough and you should add more text!
So while I’m at it, found a couple others…Chapter 16, just before §16.1 in the list there’s a loose “Linked notes” (second to last in the list) that seems to either be accidentally added or missing the explanation.
Then at the end of §16.2 (before the following subsection) in the “Getting Back to the Text,” the tip says “Note that because Scrivener always retains your selection, initially the note anchor will be selected, so be sure to press the right arrow key before continuing to type, otherwise you will accidentally delete the note you just entered (which can be undone).” I think I remember that happening in earlier 2.0 versions, but it doesn’t any longer–which is to say, unless you actively select the text to add the link to, Scrivener doesn’t auto-select it when adding the anchor, so if you’re just typing and the cursor is at the end of the word, cmd-shift-8 and then esc puts you back at the end of the word so you can keep typing without need to use the arrow key. So maybe I’m just misreading it–obviously if you had selected the text, it would stay selected–and maybe it’s irrelevant anyway, but there you are.
Looking forward to using Scrivener. Making my way through the manual. Found these typos (skipped What’s New section since I’m who’s new)
p 46 [in quotation] Nabokov [not Nabakov–unless that is a British transliteration]
p 47 line 7 of type: ‘capture’ [not ‘capturing’]
p 62 section “Trash Folder” second line from bottom: ‘that have been placed’ [not ‘that have been place’]
p 63 section 8.1.3, 3rd paragraph, fourth line: [make ‘suspicious’ into] ‘suspiciously’
p 66 section 8.3, 2nd paragraph, last line: [‘Each instance all points back’ should be–not sure exactly; just sounds odd]
p 75 section 9.2, 1st paragraph, 3rd line [Delete one ‘mode’?]
p 78 (section 9.4) 3rd full paragraph [‘rule of them’ should be] ‘rule of thumb’
The Mac one, definitely fine. Even the Windows PDF is probably stable enough now for a print job, though it probably has more by way of minor problems in it, as I’ve only just started doing an initial reading of it. It’s been write-and-don’t-look-back for some time now.
a couple more–btw I feel so supported with Scrivener–and I haven’t even started using it yet! Thanks
p 78 (section 9.4) 3rd full paragraph, 5th line [‘like’ should be] ‘as’
p 79 (section 9.4) 2nd full paragraph, 5th line [??‘functionally’ should be] ‘functioning’
p 82 (section 9.5) under Wiki Link Style, 1st paragraph, 3rd line [just an fyi: in the Helvetica font brackets look suspiciously like parentheses]
Thanks, got 'em. Actually the first two were already fixed. The third is a descriptive label, and shouldn’t have been in blue sans anyway, so it’s in quotes now.
If you could use Chapter-Section name referencing that would make my end of it easier, as that is what I can see in Scrivener and your page numbers are different than the pre-release revision I’m looking at.
p 83 section 9.5.3, 1st paragraph, 1st line [???‘within the Navigation tab’ clearer if:] ‘in the preferences Navigation tab’ [substituted ‘in’ for ‘within’ just to retain page spacing]
p 84 (section 9.5.4), last true paragraph, 3rd line [‘resources’ should be] ‘resource’
p 96 (section 10.2), 2nd full paragraph, last line [‘left’ should be] ‘right’
p 97 (section 10.3), last paragraph, next to last line [‘edit them separated’ should be] ‘edit them separately’
p99 section 11.1, 2nd paragraph, next to last line [‘strategies that is’ should be] ‘strategies that are’
(It occurs to me you can really tell I haven’t actually used Scrivener yet by my referring to page numbers. Also, please excuse all the ‘should’s’.)
section 9.5.3, 1st paragraph, 1st line [???‘within the Navigation tab’ clearer if:] ‘in the preferences Navigation tab’ [substituted ‘in’ for ‘within’ just to retain page spacing]
(section 9.5.4), last true paragraph before Section 9.6, 3rd line [‘resources’ should be] ‘resource’
(section 10.2), 5th paragraph, last line [‘left’ should be] ‘right’
(section 10.3), last paragraph, next to last line [‘edit them separated’ should be] ‘edit them separately’
section 11.1, 2nd paragraph, next to last line [‘strategies that is’ should be] ‘strategies that are’
Thought I'd pass along header typos (if that's what they indeed are) that occur at the end of the chapters, of their respective parts:
So, when we get to Part II, the heading “6.6 Compiling The Draft” bleeds into this part (part II) from the previous chapter, in this case Chapter I.
This type of run-un happens across Part III, with “13.6 Scrivener Everywhere”; Part IV, with “Chapter 21 Using Multimarkdown.”
The end of Chapter IV’s heading “Chapter 25. Printing” is presented alone with a quote from Peter de Vries; this quote should stand on its own–without a header.
There’s my two cents. Just trying to make the masterpiece shine a bit brighter!
Thanks, Marsha. All of the typos you listed are fixed.
shrumpkin: You mean the header right? If so I’ve noticed that as well. I’m sure there is something I need to tweak somewhere in the typesetting rules to fix that. It’s on my list but rather low priority right now. It seems the PART markers are not resetting the header where they should be.
The advanced section just needs help in general. I still need to re-organise stuff that should be in there from other places, and so on—or maybe just nix it altogether and move what scant bits are there to other areas. I’m leaning toward the latter as calling some things “advanced” and other things “basic” is a subjective judgement call and potentially splits topics apart that shouldn’t be split. For instance the case could probably be made that the compiler’s entire formatting pane is “advanced”. You have to understand outliner hierarchy, iteration concepts, and a number of other general computing concepts as well as a host of Scrivener specific information to even start using it—but it certainly shouldn’t be dragged out of the compile section. Meanwhile there are scant few areas of Scrivener that are completely advanced in all of their features. MultiMarkdown is probably the only thing that qualifies, but frankly that is only “advanced” if you make it so. It is quite possible to use it with no more fuss than one would use a word processor mentality. So I might just get rid of this whole section.
AmberV: Yes, the headers. It’s interesting that the Part markers don’t influence the previous header. And I agree with your assessment of the terms “advanced” and “basic”; subjective as they come.
section 12.1.1, 6th paragraph [‘editing it or view its corkboard’ ??should be] ‘editing it or viewing’
section 12.1.4, 4th paragraph [‘Determines the size ration’ should be] ‘Determines the size ratio’
section 12.2.1, 1st paragraph, lines 1-4 [unintended computer language?]
All fixed. By the way you should download the newest version of Scrivener and access Rev. 2.2-01 of the PDF. It actually predates your lists, but some of the items you’ve brought up had already been fixed as I did a big sweep through most of the text when updating the Windows text of it. So it should be a cleaner copy to work from.
But yes, that’s probably not a bad idea. Another thing that is probably worth mentioning is that any folder text will be in a file beneath the folder, since Finder doesn’t support folders with text. Added that too.
