I have finished a 61,000 word document which needs to be compiled into MSWord. To make each folder I used the template for chapters (I’ve used this on lots of previous documents). When I compile I get “Chapter 1” etc but no text in MSWord. Going back to Scrivener I click on each folder and it tells me there is no subdocument in that folder. After panicking, I did more investigation and found I could see the everything in Scrivenings, but cannot compile it to Word. Please help. How did this happen when I haven’t changed my way of working?
Hi Suze.
One possible explanation :
If you have the missing text content inside your folders (as opposed to inside a child document),
make sure “text” is checked in your compile format for the section layout to which these level 1 folders are assigned :
(In the compile panel, double-click on the compile format you used.)
. . . . . . . . . . .
Another possible explanation :
If you compile using “current selection”, make sure to include sub-documents :
Thanks Vincent, not sure if you’re using the same version of Scrivener as me, but I carried on looking after putting up the post. I’m using 3.2.3 for Mac
Under the file Heading for Compile I ticked the “Chapter” for subdocument types and this time it worked. I believe it might have changed somehow, not by me as I didn’t know it was there until I went looking.
Have now got it all set up in MS Word ready for importing into Atticus so I’m all set to go. Thanks for your help.
Suze
Scrivener doesn’t care whether a document has sub-documents or not.
A specific Compile format might care. For instance, if the format assumes that the folder document contains no text, and that the actual content is contained in one or more text sub-documents.
But you can always assign whatever Section Types and Section Layouts you think are appropriate, completely independent of the Binder structure. That’s the whole point of the Scrivener 3 approach to the Compile command: you don’t have to force your Binder outline and your output document to match.
Section 7.6 in the manual discusses Section Types in more detail; Section 23.3.3 explains how to assign Section Layouts.
9 posts were split to a new topic: Differences between v1/2 and v3 in compiling draft structure
This entire conversation misses the point.
In Scrivener 3, assigning section types based on structure can provide a convenient set of defaults, but those defaults can be overridden at any time for any document (or folder). Saying that Scrivener “cares” about structure is like saying it “cares” about the default font. Both provide a convenient starting point, but the user is in no way limited by that starting point.
In contrast, the previous approach could only assign formatting on a per-level basis, often requiring artificial changes to the Binder in order to achieve desired results in the output document.
Yes. It was a huge improvement for my workflow.