View Single Post
Old 05-19-2015, 04:19 PM   #20
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,488
Karma: 8065348
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by eschwartz View Post
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?
Try the following html
Code:
<html>
<body>
<font color="red">hi</font>
<font color="green">there</font>
</body>
</html>
At least on Chrome you will see that there is a space between "hi" and "there". Clearly the return is not being ignored but is instead converted to white space even though it is "between tags". That space will not be there if there is no return after the first </font>. If a pretty printer adds such a return then it changes the output.

I found HTML rules for white space to be fiendishly complicated. They are dependent on the rendering engine and the semantics of the tags surrounding the white space. My experience is that if the tag does not generate white space on its own (<p> does) then one may or may not see the white space implied by the returns.
chaley is offline   Reply With Quote