One thing I’ve noticed, and discussed
here at MobileRead, is that certain e-readers, such as Moon+ and Freda, don’t honor the blank line separators between different scenes in the EPUB files Scrivener makes.
One poster over there
It does not depend on Scrivener itself, but more how the blank line is coded into the ePUB. That can be done in various ways. The purists will insist you use margins to create a blank line and although they are correct, your reading program need to honor the stylesheet in order to represent it (btw, a reading program that does not honor stylesheets is a broken program in my book…). Another much used method is the empty paragraph. However, a lot of readers and reading programs will discard real empty paragraphs or paragraphs with only a space inside it (e.g.
. That is why you need to enter a special space inside it to work in all cases:
So, perhaps Scrivener has an output option for this, otherwise you need to check how it is put in the code and correct it there.
So I thought I’d go ahead and ask about that here. Is there a compile-time option somewhere to increase the likelihood that such apps won’t remove those blank lines?