From: vargenau@free.fr
To: Janis Johnson <janis187@us.ibm.com>
Cc: Joe Buck <Joe.Buck@synopsys.com>,
Janis Johnson <janis187@us.ibm.com>,
vargenau@free.fr, gcc@gnu.org
Subject: Re: http://gcc.gnu.org
Date: Fri, 04 Oct 2002 05:09:00 -0000 [thread overview]
Message-ID: <1033721766.3d9d57a6373c1@imp.free.fr> (raw)
In-Reply-To: <20021003162132.A31765@us.ibm.com>
En réponse à Janis Johnson <janis187@us.ibm.com>:
> On Thu, Oct 03, 2002 at 02:48:51PM -0700, Joe Buck wrote:
> > They are not XHTML because end tags such as </p> that were formerly
> > optional in earlier HTML versions are no longer optional. However,
> > the pages should validate against earlier HTML DTD's, such as
> > HTML 4.0 transitional. So:
> >
> > Option 2: if the page contains texinfo->html output, mark it as HTML
> 4.0
> > transitional instead of as XHTML 1.0 transitional.
>
> There's at least one problem that prevents validating as HTML 4.0.
>
> Another possibility, perhaps, is to run the processed files through
> HTML Tidy, which cleans them up quite nicely.
Thank you for answering quickly my initial message.
I tested HTML Tidy on some of your non-validating pages, and yes, it seems
to correct the pages so that they validate.
It solves at least the problems with unclosed constructs and the
unquoted attribute values.
I would suggest to always run HTML Tidy on the pages, even if correct.
With the right options, it gives the pages a nice formatting so that they
are more readable. I always do it on my own pages.
Some pages have additional problems:
- some pages lack the DOCTYPE declaration
- in page cvs.html, there are illegal "<" and ">" characters
- in page libstdc++/ you have a misplaced <a name="download">
- in page onlinedocs/gcc-2.95.3/chill.html the DOCTYPE should be first
- etc.
Thank you once again to take my remarks into account.
Best regards,
--
Marc-Etienne Vargenau http://vargenau.free.fr
Membre du Cercle généalogique norvillois http://www.cgnorvillois.org
Mes données sont indexées sur Généanet http://www.geneanet.org
next prev parent reply other threads:[~2002-10-04 8:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 10:04 http://gcc.gnu.org vargenau
2002-10-03 11:35 ` http://gcc.gnu.org Janis Johnson
2002-10-03 16:12 ` http://gcc.gnu.org Joe Buck
2002-10-03 17:33 ` http://gcc.gnu.org Janis Johnson
2002-10-03 18:11 ` http://gcc.gnu.org Joe Buck
2002-10-04 5:09 ` vargenau [this message]
2002-10-04 6:42 ` http://gcc.gnu.org Joseph S. Myers
2002-10-04 6:42 ` PATCH for http://gcc.gnu.org Gerald Pfeifer
2002-10-04 8:15 ` vargenau
2002-10-04 10:14 ` Gerald Pfeifer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1033721766.3d9d57a6373c1@imp.free.fr \
--to=vargenau@free.fr \
--cc=Joe.Buck@synopsys.com \
--cc=gcc@gnu.org \
--cc=janis187@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).