Quote:
Originally Posted by RichL
In Moon reader 2.1 you can check/un-check use of CSS.
|
I've tried that. For some reason, when I uncheck "Disable CSS," it still strips out the blank lines, even if I leave the "strip extra blank lines" option unchecked as well.
But if I use the "Preview with publisher's settings" button, there the blank lines are—but it's also locked into a small sans serif font that I can't resize or change. Weird, huh?
Quote:
Originally Posted by murg
I put in something like:
<p class="centre">* * *</p>
or
<p class="centre">———</p>
since this is targeted at an ereader, this covers the situation where the 'blank' line is at the top or bottom of the page.
The mdash method has the additional feature of not interfering with the existing asterisk scene breaks in the book. |
That's a nice idea, but I don't think it should have to be incumbent on me to manually edit every e-book I make or download—books that work just fine in Adobe Digital Editions, Nook, Kobo, iBooks, Google Play Books, eReader Prestigio, Aldiko (with "Use Advanced Formatting" unchecked), UB Reader, Marvin, Gerty, and Bibliovore—just because they
don't work properly on a couple of otherwise-excellent e-reader apps, Moon+ and Freda. I'd rather see those apps join the club and show the books with the formatting everybody else respects.
Quote:
Originally Posted by Toxaris
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. <br /> or <p> </p>. That is why you need to enter a special space inside it to work in all cases: <p> </p>.
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.
|
Hmm, there's a thought. I'll post asking about that over on the forums on Scrivener's developer site, Literature & Latte.
Quote:
Originally Posted by Jim Chapman
if you set Freda's 'remove blank lines' setting to yes, then blank lines will be removed everywhere, whether at the end of sections, or at the ends of paragraphs, or wherever. The best way to ensure that you get a blank line after some element in Freda is to set a margin below the element ("margin-below" in the CSS Style). Freda's parsing of CSS styles is a bit flakey, but it should be able to understand that (but make sure that the setting 'max margin' is set to some value other than zero - a zero value for that setting will mean that Freda suppresses all margins).
If you don't want to start messing about with margins, then probably your best bet is to use the Freda settings:
line break after para = no
force indent = yes
remove blank lines = no
This should mean that any place you actually insert a line break (element "<br>") in your file, you will see a line break. Paragraphs will not have space inserted between them, but the first line of each paragraph will be indented.
Do let me know how you get on, and by all means send me some sample files and style sheets, if you'd like me to check what exactly Freda is doing with them, and to fix the program in any places where it is doing the wrong thing.
|
Thanks for reaching out, and thanks for your willingness to look into fixing the program. I've emailed you one of my e-book files separately.