View Single Post
Old 05-19-2015, 04:05 PM   #19
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by chaley View Post
Years of experience with generating HTML tells me that whitespace between tags is not ignored, but is instead collapsed. I can't count the number of times that I had to remove returns from the HTML to avoid extra spacing between elements. Google also agrees with me, with zillions of pages talking about how to avoid the extra spaces introduced by line feeds by setting various font properties on the body tag and putting the tag closing > on the next line. And in any event, the space I was referring to is not between tags, it is a first class character in the body.

However, I could easily to be wrong now. The world has moved on in the 4 or 5 years since I last did this sort of thing, and the book rendering engines could be special purpose.
Between tags == </p> [ignoredcollapsed spaces] </body>

Considering that both calibre and Sigil explicitly add those spaces (Beautify/Pretty Print) I shouldn't think those would be a problem. Perhaps they once were?
eschwartz is offline   Reply With Quote