For some reason, the compile feature is only going up to a certain point in compiling my file, even though everything is clearly selected in the compiler.
I’ve tried this twice now and both times it is finishing sooner than it should.
Any suggestions?
The selection of what is compiled is determined by the drop-down list above the right-hand side column in the Compile Overview window, with the label Compile: That fills the list beneath it and all ‘Included documents’ - the ones with a tick in the box in front of the title - Scrivener will include in the compile.
Issues may be the selection in the drop-down list set to Current Selection without the correct selection in the Binder. Secondly, you may have a Filter active - indicated by a blue filter icon instead of gray - with a setting that includes or excludes certain files. Finally, some of your documents to compile may be outside of your Draft/Manuscript folder, which would rule them out by default.
Thanks Anton, I have tried to look at your suggestions but this has not resolved the issue. I took off the blue filter and I can definitely see that all the “tick box” documents are not being included in the compile. All of the documents are within the same Manuscript file.
I have emailed this issue to your tech support, hopefully someone can diagnose it from there?
A further question - how do I get it so that the “title” of the individual text documents is also included in the compile as a subject heading?
In the Help menu is a menu item to open the Placeholders PDF. This contains all the variables that Scrivener can use during compilation. There will be a <$title> Placeholder that you can use.
Better is to use a Section Layout with the Title and Text Content Types checked, so the Binder Title is shown above your document.
1 Like
There are two reasons why text might not be included in your output file.
The first is that you told Scrivener not to: you either haven’t included the document, or you’re using a Section Layout that excludes the text.
The second is that there’s some kind of corrupt data in the file that Scrivener can’t process. This can often be discovered by trying to compile to another format: PDF output might work fine, but not ePub, for instance. It can also be found by partial compiles: if the output stops in Chapter 5, what happens if you compile Chapter 6 by itself?
thanks Anton
I am using the <$title> placeholder as well as <$levelN_title> (as level 1, 2, 3) but still the level 3 text file name is not displaying. any thoughts why?
Thanks Kewms
Re the first reason - I don’t think its either of these as I’ve checked and rechecked the documents that are included, and the Section Layouts are working fine for the earlier files (and are formatted the same way I believe)
Regarding the second suggestion - I have noted where the document cuts off (which is halfway through a text file) and have compiled just the text file in question and the one after it, which reproduce fully. So it doesn’t appear to be a corrupt file issue either?
I will try outputting to a different medium after my morning meeting to see if that shines any light…!
There is still an open bug on that one, it never refers to the correct document when using that placeholder.
Regarding the second suggestion - I have noted where the document cuts off (which is halfway through a text file) and have compiled just the text file in question and the one after it, which reproduce fully. So it doesn’t appear to be a corrupt file issue either?
If you can drop that one section into a blank project and reproduce the problem there as well, then that would help us find what is going on and fix the bug. This blank project test could be sent to tech support.
Can you indicate when the bug for this will be addressed?
I have emailed tech support which has been very helpful. The primary issue that was causing the problems was because I was sending the file to the “printer”, then “printing to PDF”, rather than directly sending to PDF. This was an unintended error, but might help with any future troubleshooting for others!
Can you indicate when the bug for this will be addressed?
The bug report was filed around a year ago.
The primary issue that was causing the problems was because I was sending the file to the “printer”, then “printing to PDF”…
Interesting! Must be some kind of memory limitation issue with the print to PDF driver. I suppose there may be better ones you can install, but as you found, if all you want is PDF it’s better to use the PDF generator anyway.
L&L no longer gives time estimates on any particular updates or features.