public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Janis Johnson <janis187@us.ibm.com>
Cc: Udo Steinbach <udo.steinbach@ewetel.net>, <gcc@gnu.org>
Subject: Re: Website in XHTML
Date: Thu, 19 Sep 2002 23:44:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.44.0209192210550.40012-100000@pulcherrima.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20020917133100.A22888@us.ibm.com>

On Tue, 17 Sep 2002, Janis Johnson wrote:
> Thanks for pointing that out so we can fix it.
>
> This file is generated from gcc/doc/install.texi, and the problems are
> in the generated XHTML commands.  For those of you who understand what
> those tools are doing and what might be going wrong, or if the wrong
> version of the tools is being used, here are some of the problems with
> the generated html file:
>
>   - end tag for "meta" omitted, or tag not ended with "/>"
>
>   - some attribute values in meta tags are not quoted
>
>   - no </p> and </li> tags are generated
>
>   - an <hr> tag should be <hr />

I'm out of office, and for security problems I cannot access gcc.gnu.org
via SSH, but perhaps you could check whether the version of makeinfo on
gcc.gnu.org is the most current one (the package is called texinfo, but
the output of  makeinfo --version  is relevant here).

If it's not up-to-date, please ask overseers@gcc.gnu.org to update, else
it would be a good idea to contact the developers of makeinfo and report
these problems.

Thanks,
Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/


  reply	other threads:[~2002-09-20  6:14 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 [this message]
2002-09-20 11:10     ` Janis Johnson
2002-09-20 12:38       ` Joe Buck
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=Pine.BSF.4.44.0209192210550.40012-100000@pulcherrima.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=gcc@gnu.org \
    --cc=janis187@us.ibm.com \
    --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).