I use a blank line, just a carriage return, to separate scenes inside a chapter in fiction. Each scene may have more than one document inside a folder which represents a chapter. So a chapter may have 1-5 scenes, and every scene may have 1-8 documents. I prefer no ‘dingus’ icon to separate scenes.
If it is the last document in the scene as well as in the chapter, I add no blank line.
If it is one of the earlier documents in a scene (not the end of the scene), I place no blank line at the bottom of it. The only blank lines indicating a scene change then come at the very bottom of the last document in each scene (other than a scene that ends a chapter).
When I compile this to epub or mobi, this adds another blank line between those documents, which means there are blank lines where I do not want them.
In the locations where I do want a blank line (between scenes in a multiple-scene chapter, which is also a boundary between documents) it adds both that desired blank line and another, undesired blank line.
So it is adding a blank line between all documents in a chapter folder.
I tried the compile setting for removing trailing white space, yet that does not seem to be the issue here, and neither ‘remove’ nor ‘don’t remove’ gives the same result, so that seems like it’s not a part of this.
The only cure it seems would be to combine the documents, so every scene has just one document, then not add a blank line, as compiling seems to add that all on its own.
But that is not what I want. I want to maintain multiple docs per scene bc this makes it much easier to manage in the binder and outliner.
So the question then becomes this: Is there a way I can maintain multiple documents inside a chapter or scene without the compiling adding additional unwanted blank lines between them?
This seems to be a compiler issue and not an e-reader issue. My understanding is that when the compiler compiles, it stitches the docs together, which implies that any sort of marker or division between the docs would likely be invisible to an e-reader.
I can’t seem to find any explanation in the manual about this.