[LH4913] Short Story Project - Compile shifts text to new page

When compiling a manuscript using either the Short Story (Courier or Times) Project Formats, or the Manuscript (Courier or Times) Scrivener Formats, instead of the text starting after the Title and Byline, it starts at the top of Page 2. I don’t believe this is working as intended as it doesn’t match the example PDF in the Research folder. I’ve attached the test project I used to test the compile.

This is still occuring in RC14. I’m starting to think that since the text only starts on page 2, the Short Story manuscript compilation settings are actually using the settings of the Novel manuscript.

Still happening in RC19, when compiling using either the Courier or Times New Roman Short Story Manuscript settings for Word, you get a docx file with a title page, and the story text starting on page 2. Exactly what you’d expect from a Novel template, but not what you want for short stories.

I doubt this is a bug. Check the relevant section type’s Separator setting. It’s currently a page break and you want to change it to something else.

These links may help.

This shows how to GET page breaks, but removing them is in the same place.


Thanks for looking into it; however, the problem exists when I create a brand new Project using the Short Story template. Without touching any of the settings, it will produce the same issue, title page on page on, text beginning on page two. Try it yourself, with a new project. I can reproduce the problem across multiple RCs and multiple machines.

For example, here’s another project I just created as a test, without changing any settings. Also attached is the Word doc output using the Short Story (Times) format. The forum software doesn’t allow for docx files to be uploaded but the issue is present using that file type for output as well.

Not every writer wants to do it the same way you do, so the Short Story template isn’t set up the way you want it. It’s rare for any of us to get the result we want, precisely, with no modifications to structure and Compile format. Scrivener does a lot, but it can’t predict what every reader will want.

I guess I’m confused at to the purpose of the Short Story Project template then. My understanding is that it would compile into something that looks like the Sample Story Manuscript contained in the Research folder of the project, or something like this: shunn.net/format/story/ . You know, standard manuscript format, something that’s required by major markets for submitting short works for publication (some might want anonymous manuscripts but still want centered title, text starting halfway down the first page, 1 inch margins, etc). So I’m not looking for a personal preference here, I’m looking for “Industry Standard”.

If the Short Story Project template doesn’t compile into the accepted standard manuscript format" then in my view it’s a bug and needs to be reported so it can be fixed.

I compiled your test project and looked at your doc file. In both cases, the text does NOT start on page two; it’s a continuation of the title page. The section layout for it (see attachments) has no page break.

It’s working as advertised., no bugs involved.

Here I’m in Compile at the main screen, clicked “Scene” on the left. It’s highlighted and so is the attached layout preview on the right (Scene Text). It looks like nothing special: no page break, no title, no bold or centering.

[attachment=2]short story layout.png[/attachment]

Here’s the layout itself: Times New Roman 12 pt, indentation, tabs, etc. No title in the preview, and the Title checkbox is not checked, so that’s to be expected.


Here is the Separators tab, where page breaks can be turned on … but they’re not. The separator is an empty line, so there is no space between the title page and the first Scene document.


Yes, the template doesn’t do much of anything, and like you, I question why the template exists … but there is no “standard manuscript format” for fiction, poetry, or anything else. You decide what you want it to look like.

Interesting. And you’re compiling this with the RC19 Windows Beta client? I’m just wanting to make sure as the screenshots (and your forum sig) suggest you’re using the Mac version. In any case I’ll run through this again and see what I missed. Thanks again for taking the time to look at this.

We can do a Zoom session to get you started, if you like. You can find me at the “Scrivener users” Facebook page or https://www.facebook.com/DrMajorBob.

I’m using the Mac version and the result here is the same as your result.

The “Sample Story MS” clearly isn’t a sample. It’s a bit of (mis)information, that’s all.

I’m on RC19 and can verify OP’s results: Front Matter prints on first page, Scene text prints on second page,

There are no Page Break separators.

I briefly played with changes to Compile format, by changing on Page Settings Main body header and footer starts; After front matter (was On page 2), but could not get Scene to print on first page, when .docx is the target.


My bad for misinterpreting a quick (too quick) look at the OP’s doc file.

Yes, the Beta inserts a page break and should not. That’s a bug.

The problem in this case comes from the Compile > Page > “Main body header and footer starts: On Page 2”.

To workaround the bug in this case uncheck the “Different header and footer on first pages” which is indeed not needed in this project.

This bug has been filed and hope to have it fixed in the next update. Thanks!

Thanks Tiho. I’ve confirmed with the OP’s test project that your workaround causes the Scene text to print on page 1, directly after the Front Matter. :slight_smile:


The workaround does work. Thanks Tiho for the workaround, and thanks JimRac and drmajorbob for spending time to help troubleshoot.

Just a general FYI, all of the templates are in the process of being overhauled for 3.0. The templates in the current release are not always quite correct from either being just directly ported from the Mac or only slightly updated from the 1.x version for Windows when not all the compile settings were implemented in the beta or working correctly. So specific bugs aside, as far as “what are the templates good for”, they will be more helpful as starter projects and demonstrations of setting up various types of projects in the future.