View Single Post
Old 10-10-2012, 01:30 PM   #6
st_albert
Fanatic
st_albert calls his or her ebook reader Vera.st_albert calls his or her ebook reader Vera.st_albert calls his or her ebook reader Vera.st_albert calls his or her ebook reader Vera.st_albert calls his or her ebook reader Vera.st_albert calls his or her ebook reader Vera.st_albert calls his or her ebook reader Vera.st_albert calls his or her ebook reader Vera.st_albert calls his or her ebook reader Vera.st_albert calls his or her ebook reader Vera.st_albert calls his or her ebook reader Vera.
 
Posts: 544
Karma: 64420
Join Date: Feb 2010
Device: none
Besides repeating the analysis others above have recommended, what I do in similar situations is to note the last visible line in Book View, then switch to Code view and look at the same place, noting any anomalies in the code in that vicinity. Sometimes it's as simple as a misplaced > or <, or a mis-spelled entity code.

Another approach would be to expand the epub, and run the .htm file through a browser to note whether the same problem exists. The Qt rendering engine used by Sigil is sometimes more finicky than a typical browser rendering engine, or so I've found.

HTH
st_albert is offline   Reply With Quote