In the next update this will accept either shortcut, as there were some problems with Option/Alt.
** Pickiest Amendment Competition Entry**
Section 18.2.1 in the box âWant to get back to default redâ
The default annotation colour in the swatch is actually âRed Annotationâ, not âAnnotation Redâ.
I found this by accident, honest: I donât really comb through the manual in that much detailâŠ
SorryâŠ
1 Like
Picky though it may be, it will be fixed in the next revision. 
1 Like
11.4.3 FilteringbyMetadata
two
In section 10.1.1 âLinking Documents Togetherâ, in the subsection titled âLinks are Circularâ, the 3rd paragraph in that section is just â<$include>â.
§24.22.1: From this thread: viewtopic.php?f=3&t=49854 â there are two issues. The first is the Environment edit description (p.647) is wrong, you cannot edit environment items using key=var. All it accepts is a path fragment that is prepended to path.
The other one is more conceptual:
Is this really what happens? My custom post-processor scrivomatic seems convinced it is being run in the compile folder (it checks its path, STDIN etc.), not a temporary folderâŠ
Finally a very minor thing. The Headers in the manual use XX.X. Title â is that second period necessary?
Thanks, Iâll fix these, along with some 3.0.1 stragglers after the holiday break.
Yes. 
More precisely, Iâd rather figure out why spaces are dropped when copying them than changing the stock label.
Based on the confusion this user has here: viewtopic.php?f=2&t=50043 â I wonder whether a clearer description of the differences between EPub2/legacy-mobi vs. EPub3/KF8 would be worth including? I ended up referring that user to the blog, but wish I had a more pithy info box or something I could refer them to in the manualâŠ
In addition to my earlier report of the un-expanded <$include> tag, I also found 3 instances where the text contains â<$include>â when talking about the tag. See section â10.1.5 IncludingTextFromOtherDocumentsâ, where I believe the intent is to not show that leading back-slash in the compiled output.
The 3.0.1 user manual (youâll need to download it) should be all okay, with the exception of one last remaining instance I found in the front & back matter section.
Concerning the download of the manual, is the extras pack supposed to include the Scrivener manual project? If not, how do I download it? I only see options for PDF, the extras pack (which doesnât contain a project named for the manual) and the iOS tutorial project at literatureandlatte.com/lear ⊠ser-guides.
If you download the PDF version for macOS that should be 3.0.1. There were some issue with it being included in the actual update, so I uploaded the update to the server a bit later. The extras pack is just the extrasâexercises and samples that are referred to from the PDF.
So, to be clear⊠you donât have the Scrivener project for the manual available for download on the support page?
This (from âCompiling with Document Linksâ)âŠ
⊠isnât providing a link to download the project? Itâs just to help you find the PDF that Iâm already reading, and therefore donât need to download? Thatâs a bit confusing to me. I can see the text youâve included via the <$include> tag all over the place, though I canât tell which text is provided that way vs. what is in the main document, because Iâm only looking at the end result.
Nope, not yet.
Ordinarily there would be no need to download the PDF if you already have the software installed, yes. But in this case the 3.0.1 update was released without the revised version of the manual, so youâre still looking at the original 3.0 revisionâunless that has since been fixed. The copyright page has the precise revision number toward the bottom. The latest public version is 3.0.1-01b.
Do you mean to say youâve found cases where it looks like I meant to use the <$include> (rather than just talking about it) but it didnât work? I think I came across one or two instance of that but they are hopefully all fixed now in the latest PDF.
Everything in this thread in fact, save for the last few items that were mentioned before I went on holiday, should be addressed in the newer PDF.
No, this time Iâm being the confusing one. Sorry.
I assume that the text youâve added via the <$include> is all over the manual. I can see text that seems to be repeated in a couple of places, as if you used the <$include> tag to duplicate that text⊠but I have no idea IF you did that, or just copied and pasted the text. Directing the reader to go download the latest PDF (âIf you would like to see an example of this in practiceâŠâ) does not illustrate how to make use of the <$include> tag; it just shows the end result, which is not helpful to someone trying to learn how to properly use it.
Does that make sense? I thought that quote was about seeing how this looks in Scrivener.
Got it!
Oh yes, I used <$include> quite a bit for reals. To the point that I even created a custom icon to represent a type of binder item that merely links its content in from another place (I think of it as a âreplicantâ). I also took to using keywords to tag âmaster textâ items. Itâs a nice way of seeing that youâre going to have the text you are editing potentially used in another context (and Bookmark back-links let me know where check), and since I can easily view where this text might end up in the inspector, make sure the text Iâm editing fits in seamlessly with all of its intended outputs.
The quote you mentioned earlier however is for something slightly different. For keyboard shortcuts I donât use <$include> (unless for some reason I need to restate the menu command text in another location), I use <$custom:shortcut>, which gets modified at compile time to <$custom:MacShortcut>, pulling the value of the MacShortcut text string into the document that requested it. When I compile for Windows, the replacement will of course call for <$custom:WinShortcut>. The source text then just has one generic custom metadata request.
[size=80]Which, now that I look at it, I notice requires fixing as there is no âExisting Filesâ menu command, making this an appropriate and topical inclusion to the thread![/size]
⊠Not quite.
Why are you directing readers to that link? What am I supposed to find there that further illustrates how you use custom metadata for the purpose being described in that section of the manual?
Nothing at the moment. Once I get the .zip uploaded there will be a project there. The choice is between going through the whole thing and weeding out references to something that should be there, and then putting them all back in once it is, or working on getting it ready for upload. Thatâs turned out to be a bigger job than I hoped for. Part of the problem is the screenshotsâthey are all linked out to the file system, and links are absolute not relative, so even if I included the graphics (which measures in the gigs before compression) it would be a bit of a pain to have to fix all of the broken links. Iâm not sure what the best solution is there.
Okay, so Iâm not going blind⊠or my lack of ability in locating something useful isnât due to failing eyesight at least. 
Oy, thatâs a tough one. One thing to consider, if youâre willing to re-work all those paths (I know, thatâs a big âifâ), is to dump them all into a sparsebundle/DMG. I believe, when mounted, they always get attached to /Volumes, and should always resolve to the same path on any Mac. Doesnât do the Windows folks any good, but I wonder if thereâs any solution to cross-platform compatibility with external resources⊠other than talking Keith into making Scrivener able to compile images from hosted webdav/HTTP locations.
Sounds like too much work to me now that you bring it up, unless reworking your external content storage system solves some other issues for you. Maybe it would be better to just keep expanding the âextrasâ with example projects that use excerpts from the manual itself to give some context?
Found a typo.