public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <vargenau@free.fr>
Cc: <gcc@gnu.org>
Subject: Re: http://gcc.gnu.org
Date: Fri, 04 Oct 2002 06:42:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0210041247080.19611-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <1033721766.3d9d57a6373c1@imp.free.fr>

On Fri, 4 Oct 2002 vargenau@free.fr wrote:

> 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.

Readability to humans of the HTML source of generated web pages that will
only be read by web browsers hardly seems useful.  It might well make
sense to run it to make the formatting of the source in CVS that is edited
nicer, but there you need to avoid e.g. adding a DOCTYPE since the source
in CVS doesn't include the DOCTYPE, it's added in preprocessing.

> - in page onlinedocs/gcc-2.95.3/chill.html the DOCTYPE should be first

I don't expect anything to be done about regenerating the older release
manuals (3.0.x and earlier) generated with texi2html because those manuals
weren't adapted for makeinfo --html.  (Though Tidy could be run over the
generated HTML for them, since they're not going to be regenerated later
with more recent tool versions (to keep URLs stable).)  The later (3.1,
3.1.1, 3.2, mainline) manuals can be regenerated with some subsequent
makeinfo version that supports XHTML (since makeinfo --html now uses
stable URLs based on node names).

-- 
Joseph S. Myers
jsm28@cam.ac.uk

      parent reply	other threads:[~2002-10-04 11:58 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       ` http://gcc.gnu.org vargenau
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
2002-10-04  6:42         ` Joseph S. Myers [this message]

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=Pine.LNX.4.33.0210041247080.19611-100000@kern.srcf.societies.cam.ac.uk \
    --to=jsm28@cam.ac.uk \
    --cc=gcc@gnu.org \
    --cc=vargenau@free.fr \
    /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).