W3C home > Mailing lists > Public > html-tidy@w3.org > April to June 2002

Re: tidy (fwd)

From: Allan Clark <allanc@caldera.com>
Date: Fri, 17 May 2002 19:33:34 -0400
Message-ID: <3CE5934E.8895FFE0@caldera.com>
To: Dave Raggett <dsr@w3.org>
CC: html-tidy@w3.org, webmaster@danzon.com
Dave;

You're saying that Tidy assumes whether to put the </td> on its own line
based on the contents of the <td> tag.

I don't see how you've invalidated webmaster@danzon.com's feature
request to have control over this behavior.

I think what you're implying is that Tidy makes an intelligent guess as
to whether the </td> should be on its own line, and that this guess is
better than the effort of doing this feature.

My life is not impacted; just summarizing.  Don't get me wrong, I really
have no invested emotion in the outcome of this.

Allan



Dave Raggett wrote:
> 
> Tidy already checks the content for td elements to see whether
> they have block level or inline content. If the latter, the </td>
> isn't moved to the next line.
> 
>  <td><p>....</p></td>
> 
>  <td>
>  <p>...</p>
>  </td>
> 
> render the same, although
> 
>  <td>some text</td>
> 
> and
> 
>  <td>
>    some text
>  </td>
> 
> may not.
> 
> On Fri, 17 May 2002, Allan Clark wrote:
> 
> > It looks to me like this request can be summed up and compressed as:
> >
> > Feature Request:
> > please add to html-tidy a method of configuring it not to add newlines
> > or spacing before tags.
> >
> > Perhaps this could be like not using "indent".  I doubt this would need
> > a per-tag configuratoin ability (such would be exhaustive) but could, at
> > first, use a global config item.
> >
> > Allan
> >
> >
> > Dave Raggett wrote:
> > >
> > > ---------- Forwarded message ----------
> > > Date: Thu, 16 May 2002 11:23:15 -0700
> > > From: webmaster@danzon.com
> > > To: dsr@w3.org
> > > Subject: tidy
> > >
> > > Tidy almost works, but can't be used safely until this can be fixed:
> > >
> > > There's sort of a major problem with tidy in that it by default
> > > places the </td> tag on its own line, which basically destroys any
> > > fine tuned table structure in most browsers out there by adding a
> > > space, this also happens if say you have a block of text ended by
> > > </p> followed by </td>, you hopefully have noted by now in your
> > > career that the space between the last line of text increases
> > > slightly if the </td> is on its own line, as opposed to following
> > > the </p> tag, like </p></td>. This is the reality of most browsers
> > > out there.
> > >
> > > Of course, you can run tidy to xhtml specs, then reformat your code
> > > in dreamweaver, setting the break before </td> option off in its
> > > configuration file, but that's getting pretty darned obscure, not to
> > > mention a major pain in the butt, and excludes like 99% of the
> > > world's users, since almost noone can do that, or even knows that
> > > can be done.
> > >
> > > Your wrox book too had a bunch of these kinds of very subtle errors
> > > and descrepancies that make me wonder a little about the people who
> > > are making these standards. Not to mention that extremely, to put it
> > > mildly, unfortunate decision to include a free advertisement for
> > > that Mosquito product, whose connection to html and xhtml is distant
> > > at best. Fortunately O'Reilly press sometimes is able to point out
> > > some of these errors.
> >
> 
> --
>  Dave Raggett <dsr@w3.org> or <dave.raggett@openwave.com>
>  W3C lead for voice/multimodal. http://www.w3.org/People/Raggett
>  tel/fax: +44 1225 866240 (or 867351) +44 771 213 7629 (GSM)
Received on Friday, 17 May 2002 19:33:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 April 2012 06:13:52 GMT