@NogDogDec 21.2004 — #Note that this is just a method to make the source easier to read for us humans, it does not affect how the browser reads/interprets it. (Well, OK, it might add a few microseconds as it skips over those added spaces/tabs.) When I'm indenting source code, I usually use 2-space increments as I find this enough to be easily visible while allowing several layers of indention without having huge amounts of whitespace. I have seen 3 spaces recommended as the ideal amount, and a lot of places where 4-space indents are used. I think anything more than 4 is overkill, but it's all kind of a personal preference.
@ray326Dec 22.2004 — #...it does not affect how the browser reads/interprets it.[/QUOTE] Well, it [b]shouldn't[/b] have an effect but that assumes a decent browser. IE has problems with certain kinds of formating, especially in tables.
@Stephen_PhilbinDec 22.2004 — #I've always had trouble setting out my mark up in true php source, and have it properly laid out as served (x)html source. even with maticulous placement of n and t I still goof it up most of the time. :rolleyes:
@PeOfEoDec 22.2004 — #[i]Originally posted by ray326 [/i]
[B]Well, it [b]shouldn't[/b] have an effect but that assumes a decent browser. IE has problems with certain kinds of formating, especially in tables. [/B][/QUOTE] also line breaks. If you drop some text down to the next line in your document or something it can create a nasty space in ie.