On Fri, Jun 29, 2001 at 12:46:58PM -0400, Anees Shaikh wrote:
>
> So I think the problem is with malformed img tags. The parser fails
> if the tag is of this form:
>
> <img src="/library/homepage/images/curve.gif" alt="" border="0" />
>
> Note the end of the tag is closed with "/>" instead of just ">" as in
> the spec. When the parser finds the "/" it thinks it sets
> attr_name_begin to the "/" and then attr_name_end gets set to the same
> thing.
/.../
> This problem with img tags seems to be quite common (redhat.com,
> ibm.com, microsoft.com) maybe due to some authoring tools.
>
> Thanks.
Actually, I'd like to point out that the "<img />" part is valid XHTML,
which is a W3C recommendation. And thus I believe should be supported by
wget if it isn't already? If I'm not mistaken this is where the future of
HTML is heading, according to W3C. XHTML does not differ that much from
html4.01, however for non-empty elements an end tag is always required.
Thus:
<br> is wrong in xhtml
<br /> is correct (using self termination, since <br> </br> isn't valid)
and of course
<img src=foo alt=bar> is wrong in xhtml
<img src=foo alt=bar /> is correct
Consult http://www.w3.org/TR/xhtml1/ for the full description
Regards
--
Henrik van Ginhoven [EMAIL PROTECTED]
Storage for all kinds of waste http://mise.wox.org
... including humans 9799-5
