• strict warning: Declaration of FeedsImporter::copy() should be compatible with FeedsConfigurable::copy(FeedsConfigurable $configurable) in /home/writezil/public_html/sites/all/modules/feeds/includes/FeedsImporter.inc on line 94.
  • strict warning: Declaration of FeedsNodeProcessor::map() should be compatible with FeedsProcessor::map($source_item, $target_item = NULL) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsNodeProcessor.inc on line 319.
  • strict warning: Declaration of FeedsNodeProcessor::setTargetElement() should be compatible with FeedsProcessor::setTargetElement(&$target_item, $target_element, $value) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsNodeProcessor.inc on line 319.
  • strict warning: Declaration of FeedsFeedNodeProcessor::map() should be compatible with FeedsProcessor::map($source_item, $target_item = NULL) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsFeedNodeProcessor.inc on line 227.
  • strict warning: Declaration of FeedsFeedNodeProcessor::setTargetElement() should be compatible with FeedsProcessor::setTargetElement(&$target_item, $target_element, $value) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsFeedNodeProcessor.inc on line 227.
  • strict warning: Declaration of FeedsUserProcessor::map() should be compatible with FeedsProcessor::map($source_item, $target_item = NULL) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsUserProcessor.inc on line 195.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • You must include at least one positive keyword with 3 characters or more.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Declaration of views_plugin_display::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_display.inc on line 1877.
  • strict warning: Declaration of views_plugin_display_block::options_submit() should be compatible with views_plugin_display::options_submit(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_display_block.inc on line 193.
  • strict warning: Declaration of views_handler_field_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_field.inc on line 641.
  • strict warning: Declaration of views_handler_sort_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_sort.inc on line 82.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 585.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 585.
  • strict warning: Declaration of views_handler_filter_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 609.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 128.
  • strict warning: Declaration of views_plugin_style_default::options() should be compatible with views_object::options() in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_style_default.inc on line 25.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Declaration of content_handler_field::options() should be compatible with views_object::options() in /home/writezil/public_html/sites/all/modules/cck/includes/views/handlers/content_handler_field.inc on line 208.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_argument.inc on line 745.
  • strict warning: Declaration of views_handler_argument_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_argument.inc on line 770.

Compiling a DOCX in Scrivener 3

https://i2.wp.com/writerunboxed.com/wp-content/uploads/2018/07/Compiling... 300w" sizes="(max-width: 500px) 100vw, 500px" data-recalc-dims="1" />This is not my view.
Beyond a basic orientation to the software, what’s the number one thing people want help with in Scrivener?
Compile. No contest.
In April, I introduced Scrivener 3’s new approach to compiling (exporting) with a post about section types. Section types are foundational to the new compile feature, so if you need to bone up on the topic, I recommend you start there and then come back. (Or at least check it out later.)
Ready? In this second installment on compiling, I’m going to help you export your manuscript to a Word document, but the process is similar for other types of output.
Why might you want to compile to a DOCX file?

  • Submission to an agent or editor.
  • Submission to a contest.
  • To give your manuscript to a critique partner, friend, or beta reader.
  • To read through your manuscript and make notes.
  • Compatibility with Microsoft Word (duh), Apple Pages, and other word processors that will open or import DOCX files.

TIP: DOCX files are based on Rich Text Format (RTF), which is compatible across more word processors, and may do a better job of exporting images, lists, and tables than DOCX. RTF is also best when exporting for Apple Pages. If you’d prefer to create an RTF, choose Rich Text (.rtf) in step 2 of “Choosing Your Format” below.
Whatever your reason, you can create a lovely DOCX without too much fuss. I promise. Before you start, be sure you’ve set up your section types under Project>Project Settings>Section Types.
Choosing Your Format
The format determines what the final output will look like, including the margins, fonts, line spacing, first-line indents, chapter headings, scene dividers, and paper size. For this example, we’re going to choose a submission-style format.

  1. Go to File>Compile (or click the Compile button on the toolbar). The Compile window opens.
  2. From the Compile For dropdown at the top, choose Microsoft Word (.docx).
  3. In the Formats column at the left, select Manuscript (Times). This format also works for other types of output, like RTF, Print, PDF (if not creating a paperback book), and HTML.

https://i2.wp.com/writerunboxed.com/wp-content/uploads/2018/07/WU-1Choos... 300w" sizes="(max-width: 500px) 100vw, 500px" data-recalc-dims="1" />
Adjusting the Look
If you’ve never assigned section layouts for this format, you’ll see a yellow box in the Section Layouts column (center) warning you about it. Even if you have, you’ll want to ensure they’re correct for the current project.
The following image shows common elements of a section layouts “tile” and what they represent. I selected this layout because it shows most of the possible elements, but this one would work best for those who do not use chapter folders, and have one document for each chapter.
https://i2.wp.com/writerunboxed.com/wp-content/uploads/2018/07/WU-2Annot... 300w" sizes="(max-width: 500px) 100vw, 500px" data-recalc-dims="1" />
To assign a section type to a section layout, do the following.

  1. Click the Assign Section Layouts button in the center column. The Section Layouts window opens showing a tile with an example of the section layout’s settings for each layout.
  2. Select a section type in the list at the left.
  3. Scroll to find a section layout tile with the desired formatting on the right, and click it.https://i2.wp.com/writerunboxed.com/wp-content/uploads/2018/07/WU-3Folde... 300w" sizes="(max-width: 500px) 100vw, 500px" data-recalc-dims="1" />https://i2.wp.com/writerunboxed.com/wp-content/uploads/2018/07/WU-4Scene... 300w" sizes="(max-width: 500px) 100vw, 500px" data-recalc-dims="1" />
  4. Repeat Steps 1 and 2 until all section types are assigned.
  5. Click OK. The Section Layouts column now displays your choices.

https://i1.wp.com/writerunboxed.com/wp-content/uploads/2018/07/WU-5Secti... 292w" sizes="(max-width: 500px) 100vw, 500px" data-recalc-dims="1" />
Choosing Your Content
In the right-hand column, make sure you’re viewing the Contents pane. If not, click the Contents button at the top (looks like a bulleted list).
Now select the files in your manuscript that you want to include in the compiled output.
https://i2.wp.com/writerunboxed.com/wp-content/uploads/2018/07/WU-6Conte... 300w" sizes="(max-width: 500px) 100vw, 500px" data-recalc-dims="1" />
Assigning Section Types
Be sure that the section type for each file is correct. If not, you can change it by clicking the dropdown menu under the Section Type column heading.
Section Types appearing in gray italics have been automatically assigned based on your rules in the Project Settings. When you manually assign a section type that differs from the Structure-Based rules you set, it shows as black, regular type.
https://i1.wp.com/writerunboxed.com/wp-content/uploads/2018/07/WU-7Conte... 300w" sizes="(max-width: 500px) 100vw, 500px" data-recalc-dims="1" />
Modifying MetaData
Click the MetaData button at the top (looks like a luggage tag) to make sure your name and book title are correct.
Setting Compile Options
Click the gear button at the top to adjust the compile options. This is where you can include/exclude annotations, comments, and footnotes, and remove other formatting globally from your output.
Compiling
When you have everything set as desired, you’re ready to compile.

  1. Click Compile.
  2. In the Save As text box, type the output file name.
  3. Choose a location for the output file.
  4. If you don’t want the file to open automatically after compiling, deselect the option to “Open compiled output in.” Or, you can change the software (e.g. you want to open a DOCX in Pages instead of Word).https://i0.wp.com/writerunboxed.com/wp-content/uploads/2018/07/WU-8Compi... 300w" sizes="(max-width: 500px) 100vw, 500px" data-recalc-dims="1" />
  5. Click Export. All of the Compile windows disappear once your file is created.

https://i2.wp.com/writerunboxed.com/wp-content/uploads/2018/07/WU-9Compi... 300w" sizes="(max-width: 500px) 100vw, 500px" data-recalc-dims="1" />Compiled DOCX displayed in Pages
Troubleshooting the Easy Stuff
If you aren’t getting the look you want, here are a few quick things to check.

  • Have you given your files the correct section types (in the Contents pane)?
  • Have you assigned the right section layout to each section type (in the Section Layouts column, under the Assign Section Layouts button). For example, if you only wanted auto-numbered chapters but you’re getting chapter numbers and their titles too, change the section layout for your chapter folders’ section type to something like to Chapter Heading.
  • If you want the font to be the same throughout the manuscript, you can override the font settings elsewhere.
    • At the top of the Section Layouts column, there’s a Font dropdown menu.
    • Choose the desired font from the list.
  • If your front matter documents don’t have page breaks between them, make sure their section type is assigned to New Page rather than As Is.

If you can’t find a layout that does what you want, you can create your own. Right-click any compile format and choose Duplicate & Edit to create your own. If you were familiar with Compile in the prior version of Scrivener, much of this will look familiar. You can edit the section layouts under the Section Layouts tab, which is similar to the old Formatting tab.
Worst case, you can get your manuscript really close to what you want and make it perfect with a few easy tweaks in Word or Pages. Have fun!
What questions do you have for me about compiling, or Scrivener in general?

About Gwen HernandezGwen Hernandez is the author of Scrivener For Dummies, Productivity Tools for Writers, and the “Men of Steele” series (military romantic suspense). She teaches Scrivener to writers all over the world through online classes, in-person workshops, and private sessions. Learn more about Gwen at gwenhernandez.com.Web | Twitter | Facebook | LinkedIn | Google+ | More Posts

"To be able to write a play a man must be sensitive, imaginative, naive, gullible, passionate; he must be something of an imbecile, something of a poet, something of a liar, something of a damn fool."
Robert E. Sherwood

Random picks

  • Energy 2 Green is an amazing product loaded with valuable information on how you can create your own solar or wind-generated device in order to help you reduce or maybe eliminate completely your power bill every month. It provides schematics for both solar panels and wind turbines which you can make on your own in only a couple of weekends that can actually help reduce your electricity costs. The Energy2Green product supplies lists of supplies and user-friendly diagrams which you are able to follow so that you can create your own source of energy for less than $200 (for a solar panel) and $...
  • Have you been getting a plethora of promotional emails lately, claiming to be Christmas greetings? Yet when you open these emails up, you find them to be promotional emails? To be honest, these emails have been flooding my Inbox for the past few weeks! To the point that it's almost annoying to be seeing them resurfacing again and again now.
  • Every blogger knows that the difference between success and failure is getting the right kind of visitors to your blog. The following tips will help you increase the long term traffic to your blog. On-page SEO is Crucial: SEO is something every blogger must do to get traffic, unless you’re going to rely on paid traffic. SEO is a combination of off-page (which mainly means backlinks) and on-page strategies, which are equally important. Every blog post should be optimized for at least one keyword phrase that you want to rank for. If you want to get more leverage from the keywords you...
  • “It was just too damn premature. We basically spent all our time trying to explain to everybody what the problem was, leaving no time to explain how we were the solution.” –Richard Nash at Books in Browsers 2011 Richard Nash’s presentation at Books in Browsers last week garnered a lot of attention for his candid look at what did and didn’t work with his highly touted startup, Cursor, and having just watched the video, I give him credit for not simply sneaking out the back door and moving on to his next project, like so many others have already done. While the...
  • This book would have come much earlier on the psycholinguists list if I'd been able to get a copy. It's been on constant loan from the library since I started the list. It forges a rather odd ending to the list, for the material is really about deciphering an ancient script, a language, something that would have fit in more with the history of reading sections of the list.The language that is being deciphered is ancient Maya. Coe's book is an account of how it happened and why it took so long. As an entertaining read, it was a bit on the slow and name-dropping side for me; as history, it...

Recommended sites

Most recent titles

Fast fact about writing

Where, and by whom writing was first developed remains unknown, but scholars place the beginning of writing at 6,000