This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: obsolete configurations
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- To: Russ Allbery <rra at stanford dot edu>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 29 May 2002 14:02:31 +0200 (CEST)
- Subject: Re: obsolete configurations
On Tue, 28 May 2002, Russ Allbery wrote:
> I'm guessing that this is a larger issue than just this one page, but
> since I just went through working on converting my own web pages to XHTML,
> I noticed this. The XHTML 1.0 standard says:
> | In XML, URIs [RFC2396] that end with fragment identifiers of the form
> | "#foo" do not refer to elements with an attribute name="foo"; rather,
> | they refer to elements with an attribute defined to be of type ID, e.g.,
> | the id attribute in HTML 4. Many existing HTML clients don't support the
> | use of ID-type attributes in this way, so identical values may be
> | supplied for both of these attributes to ensure maximum forward and
> | backward compatibility (e.g., <a id="foo" name="foo">...</a>).
> so I think that all occurences of <a name="..."> should have a matching
> id="..." added on the pages that are striving for XHTML compliance.
I think you're right. My original plan, having been bitten by Browsers
(like Netscape 4) not supporting the id attribute properly, was to wait
until the next XHTML standard has been released and then simply convert
those "name=" to "id=", assuming that most browsers in use than will
support this then.
Also note that currently our pages are only XHTML 1.0 Transitional, not
Strict, so indeed there is quite a bit down that road. ;-)
If someone is interested in helping and providing patches, that'd be
certainly welcome!
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/