This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: PATCH: convert online docs to XHTML
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: Jonathan Wakely <cow at compsoc dot man dot ac dot uk>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Thu, 5 Sep 2002 10:28:02 -0500
- Subject: Re: PATCH: convert online docs to XHTML
- Organization: Red Hat / Chicago
- References: <20020821105235.A6802@us.ibm.com><Pine.SOL.4.44.0208212018040.14159-100000@yellow.csi.cam.ac.uk><20020822162219.GA34051@compsoc.man.ac.uk><20020831210153.A15798@disaster.jaj.com><20020905095740.GA86221@compsoc.man.ac.uk>
> The XHTML pages can be seen at http://www.compsoc.man.ac.uk/~cow/tmp/gcc/
Looks good to me...
> http://gcc.gnu.org/codingconventions.html says not to change anything
> in 17_intro without permission. I've changed contribute.html, howto.html
> and license.html, I'm pretty confident those files aren't taken from
> upstream pkgs or auto-generated, so I'm assuming it's OK?
> I didn't change the LWG lists or auto-generated pages.
>
> I changed "op()" to "operator()", and marked up a couple of other names
> as <code>. I diffed the formatted output from the pages (using lynx -dump)
> to check I didn't change any of the text, only markup. I've not changed
> any text apart from the above operator, moving a sentence out of a title
> (in "What the standard says" in 22_locale/locale.html, "See chapter 22 in
> the standard" is now below the heading, not part of it), and fixing a
> couple of spelling mistakes due to typos (e.g. "replcement")
Great.
> I could knock together a bit of text listing the main things to look out
> for when updating the docs, to ensure they're still valid XHTML. Would
> that be useful?
Yes, very.
Thanks!
benjamin