Re: anchors with the same name

Terry Allen <terry@ora.com>
Message-id: <199308182154.AA09445@rock.west.ora.com>
From: Terry Allen <terry@ora.com>
Date: Wed, 18 Aug 1993 14:53:59 PDT
In-Reply-To: marca@ncsa.uiuc.edu (Marc Andreessen)
       "Re: anchors with the same name" (Aug 18,  3:44pm)
X-Mailer: Mail User's Shell (7.2.0 10/31/90)
To: marca@ncsa.uiuc.edu (Marc Andreessen)
Subject: Re: anchors with the same name
Cc: www-talk@nxoc01.cern.ch
Status: RO
Marc, with respect, your browser puts out a lot of error messages.
What's so hard about reporting that the document is marked up
incorrectly---even if you don't report all SGML errors?

For example, I recently found that one of our editors, an 
experienced typographer, had created a set of heads that
looked like this:

        <H2>foo</H3>

Because they looked okay in Xmosaic, she didn't bother to
parse the document.  But she had an illegal, ambiguous,
construction.  Can't your parser tell when it hits something
like this?  

Even something so simple as "Markup error in [URL]" would
help, because you could go and parse the file with sgmls to
find the error.

Of course, it is good practice for publishers (that means all
of us if we put up files at our sites) always to parse their
files before archiving them.  

Regards,

-- 
Terry Allen  (terry@ora.com)
Editor, Digital Media Group
O'Reilly & Associates, Inc.
Sebastopol, Calif., 95472