Compile menu

Please (sob), please, a radical rejig of the Compile menu, so it doesn’t read like something in LaTeX. Make those Formatting levels plainly understood. Make it easy to include or exclude parts of your manuscript without crossing your fingers and eyes, turning three times widdershins and making a wish. Take out the incomprehensible language (“Override title prefix separator for updated links” - WHAT???)
Make it Mac-like. Make it work.
I’ve been going crazy for two days now trying to compile a fairly simple children’s book, with a prologue (called Prologue: Jimmy’s Day) and an epilogue (called Epilogue).
So far:

  1. the Prologue was Chapter 1 and I couldn’t stop it having a chapter number
  2. I got rid of the chapter number, but now hadn’t got the name Prologue
  3. I got Prologue back, but now the epilogue wasn’t showing
  4. And now the chapters had titles, but no Chapter 1, Chapter 2, etc
  5. I got the chapter numbers back, but now they were after the chapters’ titles…
    I’m going quietly away to have a little cry now.
1 Like

Make those Formatting levels plainly understood.

I definitely agree with the above statement. When trying to assist/teach someone how to compile, this is one, if not THE thing they find hardest to understand.

I understand the principle as I’ve used bulleted lists that use levels in MS Word and PowerPoint but I have to check preview to make sure I have the correct level ticked for the compile I need.

To the OP/Mods - I suggest that this is moved to the Tech Support section of the Windows forum. Hopefully someone there will be able to help you achieve what you wish to do with compile.

The thing is, some things in life just have to take some learning and a little effort to understand. And I’m sorry, but Compile is one of those things - there is no alternative. “Make it just work” - really, how? Work for what, exactly? For your particular project? What about everyone else’s?

Scrivener is designed to be flexible for the writing part. You can organise your work however you want. You can have folders inside text files inside folders inside folders inside text files - if you want. You can break your work down into paragraphs, into scenes, into chapters, or into a mix. A text file can represent a chapter, or a chapter can be represented by a folder containing multiple text files as scenes. You might break your book up into parts, or acts, or fitts, or whatever you like. You can write a dissertation, a novel, or a recipe book in it. And you can write in completely different formatting to how the book gets exported - if you want.

The price of that flexibility is that Scrivener cannot possibly know how the books should look on compile, because it is entirely up to you. There are two possible ways software can deal with such complexity when it comes to getting work out:

  1. Keep it simple. Just don’t allow the program to do much for the export process. Instead, just throw a couple of line breaks between each text file, call it “Export” and be done. If the user wants to do anything else with the document, they can do all of that in a different program. This is the “Mac way” of which you speak.

  2. Allow the user to take complete control of the compile process. Given the infinite possibilities of structure, this will, inevitably, involve a lot of options and a little patience on the user’s part.

Scrivener takes the second approach. But if you prefer the first approach, then just select “Original” as under “Format As” in Compile, export, open the file in Word, and do all the post-processing stuff in Word.

We have spent a lot of time on Compile, and although it can appear complex, it works, and it works well. Some things take a little learning, because if they didn’t, they wouldn’t be half as useful. I compare it to driving a car - I often wonder if all those software users who complain that software should be “simple” and “just work” because it’s the “Mac way” refuse to drive because of how complicated cars are to drive. They are complicated at first, but they are incredibly powerful and useful once you’ve mastered them…

So, no, sorry, although we will continue to refine things, we won’t be dumbing down Compile, but as I say, you can just use some simplified settings - “Original” for instance - and deal with all the formatting in Word, which will serve just as well.

I would also add that the preset Compile settings make it very easy to compile to standard novel format for most users, using common structures, anyway. It’s only when you structure things in weird and wonderful ways in the binder that you really need to get your hands dirty with the more complex Compile formatting.

And really, if you work through all of the options in the Compile pane, starting with “Contents” and working your way down, it’s not as complicated as it first appears if you take it one setting at a time. If the “Formatting” pane is bothering you, then just look at the levels in your binder and try to think: which levels are the folders at, and how do I want them to look? Which levels are the different types of text file at, and how do I want them to look? Then set up levels in the Formatting pane accordingly.

StaceyUK - I’m not sure why you are suggesting that this should be moved to the Windows forum when the op is a Mac user.

1 Like

My apologies I was reading this post from my newsfeed. Could have sworn that this was in the Windows form. My point that the concept of Levels could be explained better still stands though. It can be hard to work out what level a document is within the binder structure.


Several ways of approaching this. One would be:

You don’t have to include the folder for Compile, but now you can format the prologue and epilogue, which are at Level 1, differently to chapters, which are at Level 2 - making it simple to add different title prefixes/suffixes (thus adding “Chapter N” to chapters but not to the prologue and epilogue).

Or, if you have things split up into scenes:

Now your chapters are folders, so they can be formatted differently - and have different title prefixes - to the prologue and epilogue, which are text files with no container.

Or, if your prologue and epilogue were divided into different documents too: … 210226.png

The prologue and epilogue are still different types, being text groups rather than folders, meaning they can still be formatted differently.

If you have them all on the same level, it’s still possible:

Now, if you have title prefixes - “Chapter N” - for the chapters, then obviously everything is on the same level so you can’t apply different settings in the “Formatting” pane - in this scenario, obviously your chapter numbering will get added to the prologue and epilogue too. But you can override that by selecting “Do not add document title prefix or suffix” for the prologue and epilogue documents, in the “Title Adjustments” pane. Now the titles will still appear but without the “Chapter…” prefix for those two documents.

And of course, another option is not to include the titles at all, but write the titles into the text documents, just as you would a word processor.

In fact, I should probably stress that: there is nothing stopping you from formatting your work as you go along, just as you would in a word processor. You could just turn off all formatting by selecting “Original” under “Format As”, ensure “Separators” is set up to add a page break between your text documents, and you’re done. You would write “Prologue” at the top of your prologue document, just as you would in a word processor. And “Chapter 1” at the top of your first chapter - just as you would in a word processor. If you don’t like using Compile to do these things, then just don’t.

This sounds as though you turned off titles altogether, which you didn’t want to do if you were relying on the title of the binder document appearing in the text.

This sounds as though you added them back in as title suffixes rather than as title prefixes.

Admittedly, taken out of context, the wording of that checkbox can sound confusing. But checkboxes have to be titled concisely, and if you read that in order with the ones above it, it is far less confusing:

“Update titles in Scrivener links with prefix and suffix settings” - any Scrivener links pointing to compiled documents will be updated. So a Scrivener link saying “see Document X” might now say, “see Chapter One, Document X”.

“Do not include title suffixes in updated links” - if links are to be updated because of the above setting, don’t include title suffixes, only prefixes.

“Override title prefix separator for updated links: [ ]” - wait! If Scrivener links are updated with the title prefix, what if the title prefix is “Chapter X” followed by two line breaks? You don’t want those line breaks added. More likely you’ll want the Scrivener link to be updated to use “Chapter X - such-and-such”, or “Chapter X, such-and-such”. This setting allows for that. If you can think of an equally concise but clearer description, then please, be my guest.

And I have to say this for the record: Scrivener on the Mac is Mac-like. “Mac-like” does not mean that the software has human-level AI that can guess exactly what you want to do. If only. :slight_smile:

All the best,

I don’t really see how this could be any easier to understand, as long as you think about the levels inside the Draft folder:

If something is directly inside the Draft folder, it’s at Level 1. If something is buried a level deep, it’s at Level 2… And so on.

And the concept of levels is explained in the manual, isn’t it? Sorry, I’m not quite following this part of the confusion…

i think i,ve spotted what the problem is… those coloured dots and floating labels don’t appear on the windows version. :wink:

Indeed, the user manual even has this illustration, which makes sense to me, but then again I made it. Any feedback on what would make this confusing would be appreciated:

P.S. Excellent point, Floss. Nice of you to finally drop by!

1 Like

Some observations from a psychologist:

  1. People don’t usually read the manual. They usually expect the interface to tell them what to do, and they only look at the documentation when they have already made all sorts of assumptions about how things are supposed to work, and found that those assumptions are not giving the results they expect. Reading the manual therefore often entails throwing out the ideas they already have and adopting new ones. This is remarkably difficult, and in some cases it is never wholly achieved. (I simplify, but this is commonly what happens.)

  2. Compile in Scrivener, in one way at least, may be contrary to the “expectations” that people have built up when using other software. In my case, it took me a moment to grasp the idea that a Document could be Level 1, while there could be a Folder below it at Level 2. I suspect, though I cannot be sure, that some people may be having trouble in adapting from the “normal” state of affairs in which a Folder usually comes above a Document in the hierarchy. They look at the picture of the Folder in the interface, and don’t really see “Level 1+” after it. It would probably help if the user could see another Folder in the interface with “Level 2+” after it – that would make them realise that another level was available.

I may well be wrong, but there is certainly evidence from psychological studies that shows that existing knowledge acts as a considerable barrier to learning new paradigms.

  1. People do not see what is in front of them. There is a phenomenon called “inattentional blindness” – it basically means that if you are not expecting to see something, you will not notice it, no matter how salient it is. There are plenty of experiments by Simons and Chabris dealing with this phenomenon, and it is quite extraordinary what people are capable of missing when they are thinking about something else, or have expectations that don’t allow for something being in front of them.

Sorry that these are just a couple of random thoughts, and I’m afraid I don’t really have any solutions to offer.

I used to be a gliding instructor, and it was interesting to watch people travel along the path from being totally overwhelmed by the number of different tasks they had to perform, to complete mastery, such that they became unaware of the complexity of what they were doing. Perhaps part of the problem with compiling in Scrivener is that it is something that some of us only do very rarely (about once every five years, in my case). We thus have to relearn it every time we do it. For me, it will therefore probably remain complex, because I don’t do it often enough to make it automatic. In fact, every time I do it, the software has changed quite radically!

All the best,

I can think of countless ways to make this confusing. :slight_smile: But perhaps it would be helpful if the Draft folder itself were visible in the example binder image, as a sort of grounding point? It’s true that depending on the compile group settings, the Draft isn’t necessarily going to be the base Level 0, but it usually is, and once the basic concept of the levels is understood I think it’s easier to jump to “just compile this particular folder and treat it like it’s the entire Draft”.

I suppose there could also be a help button on the formatting pane to pop up this explanatory image without needing to refer to the manual, but I’m not sure where it could go that would fit in and I’m not sure it’s better to do that than to just go to the manual–there’s no point in laying out everything all over again when it’s already explained in detail there. But perhaps a small pop-up then with a reference to the manual might encourage seeking that source earlier in the process rather than beating one’s head against the tool for a while first? It’s much better to read a manual when not dazed and bloodied from the battle. :wink:

There you go again, twisting my words into a semblance of what some may consider to be proper grammar!

1 Like

I have to procrastinate on my novel somehow!

I have read all the answers here, but unfortunately did not understand them. I’m probably very stupid. I’ve read the manual, and didn’t understand the part about the Compile menu at all. I’ve looked at AmberV’s explanation of the plus-minus-equals bit in the Compile menu and am absolutely baffled. This, I promise you, is not because I don’t want to understand. I simply don’t understand it. (Perhaps this may be linked to the fact that I’m largely innumerate and spatially blind, and numbers arouse the same kind of horrified, baffled terror in me that this menu does.)

This is how I’ve got the chapters at the moment:

Screen Shot 2012-11-29 at 09.11.28.png

I first clicked what I thought were the logical options in the Compile/Formatting menu (given my limited ability to understand these things):

This (as far as I remember) caused the chapters to be called:

CHAPTER 1: [Prologue: Mind the Gap - but the prologue title didn’t appear]
CHAPTER 2: The Curse of the Kidds

and so on.

Obviously what I wanted was instead:

Prologue: Mind the Gap
CHAPTER 1: The Curse of the Kidds

and so on down to Epilogue, without a chapter number. (The ‘Epilogue’ scene was also (like the ‘Prologue’ scene), on the kind advice of Robert Guthrie, who’s been trying to help me with this on the Mac Tech Support forum, at Level 1, and outside a folder.)

I just couldn’t get it to work, and tried all kinds of things, changing the Compile/Contents section for the Prologue to ‘As-is’ (which moved the chapter numbering but took away the Prologue’s title, ‘Prologue: Mind the Gap’); checking the Prologue file in “Do not add title prefix or suffix to documents” in the Compile/Title Adjustments section; eventually wildly clicking random choices of files and folders in the Compile/Formatting section without success.

Eventually I said whatthehell and sent off a compiled PDF to my friend for whom I’m doing this (because he gave up, too baffled himself to tackle it) - he accepted it happily, but said the Epilogue was missing, and why was I now styling myself Keith Blount - he wrote: “The name Keith Blount, followed by ePubTest, appears on every page of the pdf you sent”.

KB, I do understand your red and blue blobs: could you possibly repeat that image and do the equivalent for the Level 1 folder, Level 1+ folder, Level 1 file, Level 1+ file and so on in the Compile menu so I can see how they relate to the Level 1 and Level 2 in the Binder?

I’m sorry to be so unintelligent as not to understand the Compile/Formatting menu. I only wish I could; I only wish it were simple and clear to me what all those folders and documents and pluses meant, and I wasn’t putting the kindly makers of Scrivener to so much work.

Hi Maelduin,

No one’s calling you unintelligent! Far from it. We’re just trying to get to grips with the confusion. Your screenshots help - I think I can see the main point of confusion now.

Take another look at your first screenshot, in particular at the “Prologue”:

Now look at the options you have ticked in Formatting:

There are three “Section Types” in “Formatting”:

• Folders
• Text groups (text documents with subdocuments)
• Regular text documents.

Each has a different icon. The icons for text groups and regular text documents are similar, with text groups being indicated by the icon being stacked.

Now look again at your “Prologue” document. Is it a folder, a text group, or a regular text document? Look at the icon.

Hopefully, upon looking at it with fresh eyes, you can see that it is clearly a regular text document - it is not stacked; it has no subdocuments itself. Its icon matches the bottom icon in the “Section Types” list of the “Formatting” table:

Note that you have not ticked “Title” for regular text documents, which is required if you want the Prologue’s title included.

If you do tick “Title” for regular text documents, of course, then this will affect those “Scene” documents, too, which you don’t want. But that’s okay. Your “Prologue” document is at level 1, where as your “Scene” documents are at level 2:

So, you need to tell Compile to add titles for your level 1 regular text documents, but not to your level 2 regular text documents. At the moment, you have titles turned off for regular text documents at “Level 1+” - this means at level 1 and at all levels below level 1 (level 2, level 3 etc). You need to select the regular text document row in the “Formatting” table (the third row) and click on the “Add Level” button:

Now you can tell it to turn on titles for text documents at Level 1 (e.g. “Prologue”) but not for text documents at Level 2+ (Level 2 and subsequent levels):

Check those settings against your binder. What these settings say are:

• Folders at Level 1+ will only have their titles included. This will affect all folders (“Level 1+”, so folders at all levels, but you only have folders at level 1 anyway, so that’s not an issue) - “The Curse of the Kidds”, “Charlie’s Chestnutts” and so on. In the “Section Layout…” pane for folders, you will want the title prefix to add “Chapter <$n>” or whatever.

• Text groups at Level 1+ - I’ve left everything un-ticked here, because from what I can see of your binder screenshot, you don’t have any text groups to worry about, only folders and regular text documents with no subdocuments.

• Single text documents at Level 1 - this will affect your “Prologue” (and your “Epilogue”, I’m guessing), because that is at level 1 inside the Draft folder. I’ve therefore ticked both “Title” and “Text” since your prologue contains text and you want its title included.

• Single text documents at Level 2+ (level 2 and subsequent levels) - this will affect your “Scene” documents, which are single text documents, as you can tell by their icon and the fact they have no subdocuments, which sit at level 2 (they are inside folders, unlike “Prologue”). Thus I have only ticked “Text”, as the titles for your chapters are being added by the enclosing folders.

No problem, although hopefully the above has helped too:

The main thing to remember about the levels in the Compile pane is that you can add or remove them, using the buttons in the top-right of the levels table. The last row for each of the three document types (folders, text groups, and single text documents) will have a “+” after it, indicating that the formatting and options for that level will also apply to all lower levels.

This was probably your problem and the source of your frustration - perhaps you didn’t realise you could add other levels to that list? Your project is set up so that you need your text documents on level 1 (the prologue and epilogue) to use different formatting and options to the text documents on level 2 (the scenes), so you needed to add a “Level 2” row to the formatting table in order to achieve that.

This sounds as though you created the project a little while ago. I accidentally left my name in one of the templates in an earlier version, d’oh. This you can edit in the “Page Settings” pane, though, which allows you to customise the header and footer.

How about this? If you are still confused, send me your project - or a dummy project using the same document structure but with gibberish text - along with an example of how you want it to look when it is compiled, and I will set up the Compile options for you and turn it into a tutorial that we can put on our knowledge base?

All the best,

Thank you very much, Keith (and all others); I’m going out for a calming walk by the sea, and will then come back and read your post in detail.

I’m wondering if it may be possible that my Scrivener’s just gone rogue; for instance, the search-all-documents search has completely stopped working. I just searched for “Gene Sharp” (having copied in Sharp’s complete book From Dictatorship to Democracy in a file named ‘Gene Sharp’, which of course contains the words “by Gene Sharp”) and it failed to find any reference to him in the project. Navigated down to the bottom, and there was the folder and its contents.

It seems to me that Scrivener is essentially two different programs (it’s not, but it helps me to think as if it is):
#1: software to help you prepare your draft free from the distractions of formatting and without constraints on structure
#2: software to take your manuscript and apply structure and formatting to it.

Part #2 is the Compile functionality. #1 is everything else.

The trouble is that the structure that makes the most sense to you for organising your writing might not be the most appropriate structure to achieve the vision you have on compilation. This is more likely to be the case when you start to include things like Prologues, Appendices, and other things which you may treat exactly like any other Chapter while writing, but for which you need completely different title elements, formating and page layout options.

So, you are left with three choices:
#1: Set up your structure at the beginning so that the Folders, Files and layout in the Binder matches your eventual vision for the compiled book.
#2: Write your manuscript the way that makes sense to you, and then re-arrange the binder at the end to suit the compilation you want.
#3: Set up compile settings that get you most of what you want based on your preferred writing structure and live with that.

I don’t believe that any of these options is ‘perfect’ or aligns to the vision KB has for the software. Each has their problems…
#1: It’s against the Scrivener philosophy of ‘write without format or structure constraints’. Added complications if you want to produce more than one format output.
#2: Moving things in the Binder is easy, but it’s destructive editing. This approach only works if you intend to compile only at the end of the writing process, as opposed to compiling works in progress at various stages of development.
#3: It’s a compromise.

So here is my Wish List item. Well, in fact I have two of them. Maybe three. Okay, actually it’s four…

#1: Collections! You can set up individual Collections for each of your intended compile formats, and you can re-order them to your heart’s content without affecting your Draft. However, there are two things you can’t do to them: change them from folders to files (and vice versa), or change their level in the compile heirarchy. If you do these in a Collection without affecting the Draft, you could have a lot more flexibility between writing as you want and compiling as you want.
#2: Even if you don’t implement #1, it would be helpful to those of us that use Collections to compile to have the level of the documents visible in the Collection as opposed to the flat list. (I guess this would need to be an option to switch on/off?).
#3: I’d like to be able to disconnect the level of a document from that of a parent. At the moment, the maximum level a document can be for compile purposes is 1 higher than its parent. I use different levels to drive different formating. See the example here from the recent NIAD which uses levels to allow a section to have different indentation and formatting:

The trouble is, if I wanted to start a chapter with a section like this, I’d have to manually format in my draft and not have compile override (which I don’t want to do - especially when I intend to compile to various different formats), or I’d have to insert blank files as parents - which would give me extra line breaks due to the transition Separators between documents. If I could have a level 4 document immediately following a level 2 document, I could have a much greater degree of flexibility on the compile process. Incredibly useful when people insist on including quotations in their NIAD chapters :smiley:
#4: In order to make the levels even clearer than they are at the moment, perhaps some gentle column shading in the binder? You can have a on/off switch for purists. You have to admit, the diagram you produced did make it easier to read!:
#5: eBook contents pages! At the moment the title of the entry in the contents page is just simply take from the title of the document (on the Windows version - not sure on the Mac). It would be great if this could also include whatever title prefix and suffix you have set up. Using the Title and ony the title, means that all the info you want to use (including things like the words “Chapter” or “Part”, or any numbering placeholders) needs to be in there - meaning less flexibility - and greater disconnect from how you want to write to how you want to compile.

Okay so it was five.

This wouldn’t work - there’s a good reason collections are flat lists. Collections are arbitrary lists of documents. If they allowed hierarchies, whole structures could be destroyed by deleting a document in the binder, and each document would have to remember that it had an infinite number of possible children depending on what collection was being shown. It’s just not really practical, and would add complexity rather than reduce it anyway.

I don’t understand why you would want to do this. It would also make things more confusing, not less confusing. At the moment, you look at the documents in the binder and can count down - here is a level 1 document, here is a level 2 document, and so on. But you are saying that you want a document that is at level 3 in the binder to be treated like a level 4 document? That would be weird, and confusing, and I’m not sure how it would confer any advantage.

But realistically, how often would you ever want to do that? I don’t think this comes up enough to justify adding such complexity. And it wouldn’t be possible in the binder to have a sub-document appear as a sub-sub-document without a container in-between - that’s antithetical to the folder/file structure and would require a completely different binder structure, more of an indented list structure than a file/folder structure.

I’m not sure if there is a bug in the Windows version here, but on the Mac version you wouldn’t get those extra lines. You would just set the blank document not to be included in Compile (in the “Contents” pane or via the inspector) and it would be treated as though it were not there. So there is an easy workaround for these rare situations that doesn’t require trashing the entire binder organisation and replacing it with something else. :slight_smile:

This sort of thing is useful in diagrams, but it would be very bizarre in the binder itself, I think - it would also go against UI standards.

This is a Windows limitation. It is there on the Mac, and I was explaining up-thread about some of the options relating to this. On the Mac, you tick a checkbox to tell Compile to add in the title prefixes for Scrivener links (which also affects contents pages in e-books), and determine a separator to go between the prefix and title instead of blank space or empty lines.

All the best,

If you allowed the disconnect between the level of a document and the document above it (wish#3)this wouldn’t have to be the case?

I think of it as adding flexibility

It could be more confusing, I grant you (hence Wish#4). The advantage is simply I have more control and flexibility over the formating of my manuscript and am able to write one way and compile another.

You’re right of course that it’s less common. Books like Dune by Frank Herbert that use such things tend to use them for all chapters rather than the occasional one. I suspect this is more common in non-fiction than novel writing.
Again, I think of it as providing extra flexibility rather than complexity (the advantage of not being the guy who has to code it, I guess).

A Scrivener project doesn’t actually create folders and create a heirarchy in the files on your computer. It’s a simple list of text files and an overarching table of contents that says what to do with them. The file format would need to change, I see that. As I understand it the TOC works in the heirarchical nature using commands to nest files in the binder. The BInder is essentially a linear list from top to bottom - could the TOC not just say for each position in the Binder which file to look up, what type of file it is, and what level it is?

True. But this is the place for wishes! :smiley: I just don’t like the idea of having things in my Binder that aren’t there to hold some sort of content.

Yeah, it would require a major format overhaul. But you like coding, right? :smiley:

Agreed - just included as I think it would be necessary if you allowed wish#3.

Fair enough

Basically, my suggestions are about trying to set up Scrivener in a way that enables me to write in a format and binder structure that suits me, rather than setting it up to suit my eventual compile requirements, which may change depending on different export formats, audience and use, and may evolve during the process of writing the document. I’m guessing from your answers, though, that you don’t really agree with this initial premise, and therefore I am trying to solve a problem that you don’t think exists… in which case, fair enough!

No, no, I know no one’s accusing me of being unintelligent - I’m just explaining that I am. I’m bright enough when it comes to words, but anything involving numbers or spatial sense leaves me confused.

Your explanation below is really good and helpful - thank you - but I still have a couple of questions, if you don’t mind.

I don’t understand this, quite. When I make document A into a subdocument of document B, the result is that document B turns into a folder. What are these text groups, please?

So I don’t turn on titles for Level 1+ in the document group, but I do for Level 1+ in the folder?

I don’t now, but my friend seems to be trembling on the edge of asking me to divide some of these scenes into multiple scenes. Would that make a difference? And if so, what should I tick? (I understood - or thought I understood - that ticking Level 1+ affected everything subsidiary to it. But I may be becoming confused between the Level 1+es in folders, document groups and single documents, which I am still really failing to grasp properly.)

Aha - that’s what I thought. So if I checkmark the folder at Level 1+ (in other words, the top level), won’t that cause that ‘Chapter 1’ stuff to start up there, and include the Prologue scene and the Epilogue scene? (I’m not really understanding how the 'Chapter 1…2…3… titles relate to the folder titles.)

I’ll have a look at the “Page Settings” pane. But no, I created this project three long harrowing days ago… oh, wait, there is no “Page Settings” pane; had forgotten that. So I’m stuck with my alternate personality as KB :slight_smile:

That’s a very generous offer, which I’ll take up - thank you. It will, though, have some sub-scenes, because my friend wants to divide up the existing scenes in some cases.

Edit: I’ve tried compiling it like this; unfortunately, while the prologue now has “Prologue: Mind the Gap” as its title, it also has:

"Created: 4 November 2006, 16:33
"Modified: 28 November 2012, 16:20
"Status: First Draft
“Label: Scene”

before starting into the prose of the prologue; kind of kills the mood.

Oh, wait, got rid of that; for some reason “Meta-Data” was ticked in the last two levels. Have unticked them.

Just my 2 cents, but I think this could be clearer if the “Example Binder” section of the shot had sample document names/titles/something besides “Level 1, etc.”. Having the same “Level 1, Level 2” I find confusing, until I figured out that I was looking at the “Binder” instead of the compile box. Yes, I know it’s labeled, but having the names match exactly leads me down the path of “they will match that way in what I’m looking at” where in the real world, it is highly unlikely that they will match (assuming most people don’t name their chapters “Level 1”, etc. :slight_smile:)

Anyhow, that may just be me, but wanted to toss it in for consideration.