Nope. Only, I'd add that there are existing apps out there that will fall into various server-side languages to do intelligent replacement of linebreaks -> paragraphs, smart quotes, etc. KSES, used by WordPress (or at least it used to be) is one such for the PHP langauge ( http://sourceforge.net/projects/kses ) -- and I'm sure there are others. I don't think we should excuse server-side pages in that respect altogether, but generally agree with your sentiment.
Josh On 1/14/06, Peter Firminger <[EMAIL PROTECTED]> wrote: > The much maligned <br> element is essential in our work. Sometimes we're not > just doing poetry and addresses. > > Take for example the archive page of this very message (the one I'm replying > to). > http://webstandardsgroup.org/manage/archive.cfm?uid=C69ACE78-BB9A-910B-E6CC1A4A59BDF099 > > How else would I accurately display Lachlan's example below without <br>. I > don't agree that <pre></pre> is the answer because this may well force the > page into breaking due to width. Pre is pretty powerful and can break a layout > very quickly if something unexpected is forced into it. > > _____ > > The common usage to separate paragraphs like this is wrong: > > <div> > paragraph 1<br> > <br> > paragraph 2<br> > <br> > paragraph 3 > </div> > > In most cases, if you ever get the feeling to use 2 consecutive <br>s, > _____ > > > (here it is in case you don't want to look at the archive) > > _____ > > The common usage to separate paragraphs like this is wrong:<br /> > <br /> > <div><br /> > paragraph 1<br><br /> > <br><br /> > paragraph 2<br><br /> > <br><br /> > paragraph 3<br /> > </div><br /> > <br /> > In most cases, if you ever get the feeling to use 2 consecutive > <br>s, > <br /> > _____ > > I could replace <br /><br /> with </p><p> (and I usually do... There was a > reason I didn't in this case but I can't recall now) > > Remember, we are not marking this up by hand, we have to make sure it always > works no matter what is thrown into it as content. I get the feeling that a > lot of the time people focus too much on what is hand coded in static HTML > pages (and therefore very predictable) when making assumptions like "<br> is > bad" and even including <hr> as bad. > > Broaden your view to what may be churned out of a CMS or other server-based > system (a web-mail interface etc.) > > A line break is semantic in my view. In the case of the aformentioned page, I > believe it is very much like the poetry example. I'm expected to display the > email the same as it was written (within the limitations of the page > boundaries). > > In this context, any arguments? > > P ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
