From: Joe Buck <Joe.Buck@synopsys.com>
To: janis187@us.ibm.com (Janis Johnson)
Cc: pfeifer@dbai.tuwien.ac.at (Gerald Pfeifer),
janis187@us.ibm.com (Janis Johnson),
udo.steinbach@ewetel.net (Udo Steinbach),
gcc@gnu.org
Subject: Re: Website in XHTML
Date: Fri, 20 Sep 2002 12:38:00 -0000 [thread overview]
Message-ID: <200209201813.LAA17387@atrus.synopsys.com> (raw)
In-Reply-To: <20020920110557.A1441@us.ibm.com> from "Janis Johnson" at Sep 20, 2002 11:05:57 AM
> The texinfo documentation says "The HTML generated is mostly standard
> (i.e., HTML 2.0, RFC-1866)." It looks like we should use different
> headers for html files generated by makeinfo, and don't include the
> compliance claim in the footer.
Omitting </p> and generating <hr> instead of <hr /> is valid HTML 2.0.
If we want to be XHTML-compliant, we'd need to get texinfo fixed.
next prev parent reply other threads:[~2002-09-20 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 12:59 Udo Steinbach
2002-09-17 13:30 ` Janis Johnson
2002-09-19 23:44 ` Gerald Pfeifer
2002-09-20 11:10 ` Janis Johnson
2002-09-20 12:38 ` Joe Buck [this message]
2002-10-04 4:58 ` 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=200209201813.LAA17387@atrus.synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gnu.org \
--cc=janis187@us.ibm.com \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=udo.steinbach@ewetel.net \
/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).