View Single Post
Old 08-03-2008, 08:12 PM   #7
llasram
Reticulator of Tharn
llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.
 
llasram's Avatar
 
Posts: 618
Karma: 400000
Join Date: Jan 2007
Location: EST
Device: Sony PRS-505
Quote:
Originally Posted by IceHand View Post
However, the downside of your change is that the resulting HTML file often has very long lines and is hard to read.
The problem with the '> <' to '>\n<' trick is that most LIT files don't actually contain such whitespace. (In fact, I was pretty surprised when Mobipocket books did -- I think it must be due to a quirk of their rendering engine.) Inserting a newline after block-level elements like <h1/> and <p/> will probably usually be safe, but it's possible (if crazy) to have CSS like 'h1 { display: inline; }' which would make it no longer safe.

How would you feel about an option to run the markup through a pretty-printer on output?
llasram is offline   Reply With Quote