This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [wwwdocs patch] adding a table of contents to the projects file
- To: Dan Nicolaescu <dann at godzilla dot ics dot uci dot edu>
- Subject: Re: [wwwdocs patch] adding a table of contents to the projects file
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Fri, 23 Mar 2001 10:24:47 +0100 (CET)
- cc: <gcc-patches at gcc dot gnu dot org>
On Wed, 21 Mar 2001, Dan Nicolaescu wrote:
> I have added a table of contents to the projects/index.html file.
> When doing this I changed some <li>s to be <h[23]>, so that they
> appear in the TOC.
> It makes it much more readable now.
This is fine (as we discussed off-list), but I note a couple of markup
problems, see below...
> I also added a new section for "Work in progress" and added pointers
> for some stuff that I saw on the mailing list that is going on.
> Please add some more to that list.
This is also a good idea, though I'd prefer to split this into two
patches.
> ! <H1><A NAME="toc">Table of Contents</H1>
> ! <UL>
> ! <LI><A HREF="#tocref1">Fix bugs in the GNATS database</A>
Please use lower-case letters for markup, that is,
<h1><a name="...">...</h1>
<ul>
<li><a href="..:">...</a>
> + <h2><A NAME="tocref1">Fix bugs in the GNATS database</h2>
> <p>You can investigate bugs in our <a href="../gnats.html">GNATS
> database</a> and attempt to fix them or see whether they still are
> present in current GCC.
This hasn't been introduced by your patch, but we should have </p> here.
> ! <h3><A NAME="tocref18">Fully document the interface of front ends to GCC</h3>
> ! Fully document the interface of front ends to GCC (that is, the
> <code>tree</code> interfaces, and the various functions, hooks, etc.,
> that a front end must or may provide). <code>gcc/c-tree.texi</code>
> includes some of this information; <code>gcc/LANGUAGES</code> contains
> incomplete information about changes that have been made to this
> ! interface.
This has been changed by your patch, and we do need <p>...</p> here; there
are a couple of occurrences of this problem.
Would you mind making these change (and the change to use more expressive
labels you mentioned) and resubmit these patches?
I'll be offline starting tomorrow, but perhaps someone else (Zack?) can
install your changes then?
Thanks,
Gerald