- From: Alexander Biron <biron@ifh.de>
- Date: Thu, 14 Sep 2000 08:25:13 +0200 (MEST)
- To: "Richard A. O'Keefe" <ok@atlas.otago.ac.nz>
- cc: html-tidy@w3.org, saexpress@netscape.net
Hi, On Thu, 14 Sep 2000, Richard A. O'Keefe wrote: > Chris Matson wrote: > Pretty layout problem > > <!-- comment goes here --> > <!--#include file="footer.inc" --> > <!-- another comment goes here --> > > when TIDY'd (? sp.) looks like this > > <!-- comment goes here --><!--#include file="footer.inc" --><!-- another > comment goes here --> > > Certainly a problem, because the two have different content. > Put this in an element: > <PRE> > <!-- comment goes here --> > <!--#include file="footer.inc" --> > <!-- another comment goes here --> > </PRE> > This has content > '\n' '<!--#include file="footer.inc" -->' '\n' > in HTML, or > '\n\n' '<!--#include file="footer.inc" -->' '\n\n' > in XHTML. The flattened form loses some of the newlines. > Does Tidy always do this, or only in elements where spaces are > squished (<P> and the like)? Maybe I miss something, but an include file normally contains HTML, e.g. the content of a navigation bar. When you put this between <pre> and </pre>, you can get into trouble with the document the server finally transmits to the user. In this case I would not change anything with the HTML source, but would really like to see tidy change. Here we are only concerned with the pretty printing function of tidy. I don't know of any instances, where authors want their comments to be moved around (like being appended to the end of the previous line. So I would like to see tidy change to leave comments where they are. The only issue one might argue about is indenting. BTW, for this purpose, include statements are just comments. -- Cheers alex Alexander Biron Support the ban of Dihydrogen Monoxide: http://www.dhmo.org/ work: http://www.ifh.de/~biron/ private: Tel (+49)33762-77-233 Tel(+49)30-4948857 mailto:biron@ifh.de mailto:biron@frohnau-flamingos.de
Received on Thursday, 14 September 2000 02:25:31 UTC