View Single Post
Old 12-21-2016, 09:50 PM   #7
Trane
Groupie
Trane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensions
 
Posts: 165
Karma: 51147
Join Date: Dec 2016
Device: android tablet
Quote:
Originally Posted by Notjohn View Post
I've been using Sigil for almost five years and maybe twenty books, and I have never seen it do any such thing. I would suspect the underlying code. Did it come from Word? Calibre?
The original code pasted into Sigil worked fine for almost 2 weeks. It was only after I copy/pasted the Appendix section into the body, and then only the h3 headings were not formatting. But again, it's fine now. (However it's still inserting blank lines - more on that later.)

FTR wrote in Word, saved as Text, opened the text file and copied the text back into a new Word doc as text, then used the Toxaris EPub add-in to Word to generate clean HTML. Pasted that HTML into Sigil.


Quote:
Originally Posted by JustinThought View Post
That sounds similar to a problem I was having, that I posted in another thread. What was happening was, Sigil was doing some housekeeping each time I saved, and placing a blank line before a certain section. This was code that wasn't inside a <p> tag, but instead in a <div>, but that div was way up on the page. I ended up just placing the errant code inside a dummy <div>, directly before and just after the section that was being spaced out, and it has taken care of the problem.

Any similarity to your code? Find the place where the blank areas are being made, clear them out, then repeatedly hit ctrl-s to save and see if it doesn't move down. If so, you're running up against the same problem. Use a <div> </div> to bracket that section, and it should go away--which may solve your other problem as well.
You are definitely on to something as to when blank lines appear. I just went into Code view and scanned down, and again it has put in stretches of blank lines in certain places, (not where they were before).

Took out the blank lines in one spot, hit CTRL+S and it inserted a blank line above somewhere, b/c all of the HTML lines showing in the window shifted down (jumped line numbers downward like a line was inserted further up).

And the number of blank lines that crop up correspond to about the number of times I have saved (both yesterday and just now when I noticed I had stretches again, but the stretches weren't as long as before b/c I have saved fewer times between).

Haven't tried the <div></div> tag as a fix, as the blank lines (or the sections of several blank lines) are not relegated to appearing in the same part of the book each time.

EDIT: FTR when I say blank lines I don't mean one, and I don't mean it cleans up the code so it's easier to read. It inserts lines with nothing on them whatsoever, and it keeps inserting a new line next to the other one with each consecutive save. So there are huge sections of blank space, and it does this in various places. If I delete all the blank sections, it starts creating new blank sections in new spots... adding one line per each blank section "it's building" every time I save.

Also FTR [in case it matters] this is a long book, over 75k words/~115 Word pages.

Last edited by Trane; 12-21-2016 at 10:10 PM. Reason: clarify
Trane is offline   Reply With Quote