I’d like to compile the “Win” version of the Manual project, and I can’t figure out where the filtering with labels can be configured.
So, if s.o. could tell me the menu / dialog box I have to look for, that would be very helpful. Thanks!
Looking at a blog entry about compiling options
gwenhernandez.files.wordpress.co … -29-pm.png
I think this feature is simply missing in the Windows version (and in the current Beta).
IMHO this is a crucial feature, or, to put it in the terms of Autodesk - I do some SME work for them occasionally - it’s definitely “the rice”, not “the wine” 
.
Which feature ,as the content pane is definitely there in the Windows version.
The contents pane is indeed there, but below that in the screenshot you’ll see a “Filter” option. That lets you exclude or exclusively include items based on various attributes, such as their label, status, presence within a collection or binder selection (prior to calling up the compile panel). The user manual project uses labels to determine if a section is exclusively Mac or Windows focussed, and so without that feature you’ll end up with a lot of nearly-duplicate and irrelevant articles from the other platform. I should update the readme file at the top of the binder, as it was written prior to Windows launch.
If it isn’t too much effort, could you provide a “win only” version of that manual project? I’d really like a bigger project to test some publication strategies:
-
Scrivener > Kindle
-
Scrivener > MMD/LaTeX > PDF readable on Kindle
Yeah, that would be a lot of work, even just making a public version of the project as-is takes some time (which is why it is usually a bit out of date; my working copy is a lot more messy). As it is right now when I make edits to overlapping areas (which are fairly considerable), both manuals benefit simultaneously. If I forked it into two different projects, then I’d have to do twice the work and I can barely keep up as it is. It wouldn’t be so hard to strip out the Mac-only documents by searching for that label and trashing them all, but the real tough part would be the thousands of inline annotations that selectively hide everything from features to keyboard shortcuts from one platform or another. For instance when I say, “You can toggle the visibility of the inspector with Ctrl-Shift-I” That actually looks like “You can toggle the visibility of the inspector with [MAC:Shift-Cmd-I][WIN:Ctrl-Shift-I]”, only one of which appears in the final copy depending upon the choice of output. The way annotations are used are another area that wouldn’t quite work in Windows yet, as it doesn’t handle multi-line notes. I use them, in addition to platform specific text, to block out whole chunks of text for special purposes, like indented sections or tip boxes.
The interactive tutorial is a non-trivial project. I forget exactly what it clocks in at, but I think it’s around 15,000 or 20,000 words. Not quite a book, but a hefty chunk of one, and being already designed for a normal rich text output path, it’ll be a lot easier to experiment with the Kindle using the .mobi export option. For MMD, poke around on Fletcher’s MultiMarkdown site. There is a Scrivener project demonstrating basic usage. It doesn’t do anything fancy like the manual does.
Anyway, I don’t mean to completely shut down your idea. Ultimately the .scriv manual will compile on Windows the way it should (though probably with a Perl install because it needs XSLT in its current form to handle some of the aforementioned text switching), and though it may take some time for that point to arrive, I’d rather continue to focus on overall improvements to it (like more screenshots and such) than trying to maintain two separate copies. If my whole job was the manual that would be one thing, but it is unfortunately only a small percentage in the grand scheme, so time must be allocated carefully.
I love how many polite words Ioa spills just to say, “Sorry, no.” 
Ioa,
I appreciate elaborate answers, and, in my POV, there is a plan b:
Implement the “filter” function in the Windows version and no source docs have to be changed
Cheers,
Franz-Josef