Compiling for Print Cuts off pages

The work around is to compile to PDF and/or Word, but if I want to compile for print, I loose the last couple of pages of the selection. Tech support has been able to duplicate the problem, but they’ve not come up with any viable solution that I’m aware of. If someone could suggest what I’m doing wrong, I’d really appreciate it. I’ve attempted to compile using different setting all with the same results.

It would be nice if this were fixed. Once I finish a project, I’d like to compile the complete book. If it does this for printing, what will it screw up for finalization?

You are not doing anything wrong. It is an old known bug.

Compiling to PDF then printing won’t mess anything, no. But just don’t use the browser or app you are viewing the result in print dialog (ctrl+P). Make sure to use the system’s one : ctrl+shft+P

Thanks for your reply. I actually have a program on my computer I use to work in PDF files. So that’s not a problem.
I print one scene at a time for critiqueing, and I’d use the print current document/selection, but it cuts off the last line on random pages or prints half the line on the bottom of one page and the other half on the top of the succeeding page. Not useful at all. And I haven’t figured out how to format the page to prevent it. Sigh.

Never had these problems in Scrivener 1. But I still prefer the newer version.

Do not compile to print. Simple as that. Compile to PDF, then print the PDF.

1 Like

That’s what I’ve been reduced to doing.

Welcome to the club. :wink:

1 Like

Now that I think of it, even better than compiling to PDF, is for Windows users to compile to RTF.
(For convenience, you can set the compiler to auto-open the compiled document in the default app; last checkbox at the bottom of the compiler’s option.)

Auto-open compiled document


Then, using LibreOffice (free and open source), you can do two very convenient things:

1- Tell it not to split your paragraphs across pages. (I personally find it annoying, when I print a revision copy to further work a chapter longhand, to have a paragraph part here, part there…)

Do not split paragraphs. (LibreOffice screenshots)


2- Where straight out of Scrivener you’d have to either print all or split the source document, in LO* (or pretty much any, if not all, wysiwyg text editor) you can print only a segment of the whole compiled document if that is what’s needed.

Print only part of a compiled document.

Ever since I figured out how advantageous those two were, I have not been compiling to PDF for print no more.

Another trick (why not) in the context of personal use prints:
Designing a compile format so that your text color output is red (I use red, see why below, else use any shade of grey instead of black) to then print in B&W (printer’s setting) saves ink.
After extensive (or somewhat) testing, I concluded that this is the best readability/darkness/ink-ratio color:
(My eyes, my personal preference.)

Optimal color for personal/revision prints.


Note that the way I use it, I apply that color right in the editor (I don’t use a dedicated compile format as I said could be done above).

Why red and not just grey? And why right in the editor?

1- Since I do a lot of back and forth between longhand and Scrivener, no risk of a mix up, where I’d work on a chapter that is actually printed → If the text is red, it means it is somewhere printed, undergoing longhand editing, so I just don’t touch it in Scrivener. (Red means don’t. – Obvious and simple.)

2- It makes it easy to later spot the text selection you intend to print once in LO*.

(* LO is short for LibreOffice.)

Enjoy. :wink:

1 Like

Thanks for that tip. I actually have Word on my computer. Needed to have it for work once upon a time, and I also need to convert things to Word periodically to send to other people. And one of my critique groups members trusts me to edit her papers for college. Of course, she uses Word. And another of my critique group members uses that old Microsoft program, Microsoft Works. I don’t have it, but I have an add on in Word which will open his files. Which I then convert to Word to send to other members of the group.

So far, compiling to PDF works, and it helps me keep up with what I’ve taken to the group for critiquing. As long as there are viable work arounds, I can handle it. However, I just might use this tip for when I print up the whole chapter.

Again, thanks.

I just upgraded my computer, as in jacked the old one up and installed a new one under it. The new one runs Windows 11 Pro while the old one ran Windows 10 Pro. So, as an experiment, I decided to compile to print a scene from my current work in progress. And it still didn’t print all the pages. I know this is an ongoing bug, but is there any hope that it will ever be resolved?

There haven’t been any updates on that ticket since it was posted. It should be looked into though, quite soon in fact.