From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: jimb@zwingli.cygnus.com
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [Jim Blandy <jimb@cygnus.com>] RFA: Don't pass -glossary flag to texi2html
Date: Thu, 11 Oct 2001 23:39:00 -0000 [thread overview]
Message-ID: <5567-Fri12Oct2001083936+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <nphet5d83m.fsf@zwingli.cygnus.com>
> From: Jim Blandy <jimb@zwingli.cygnus.com>
> Date: 11 Oct 2001 19:18:05 -0500
>
> Andrew Cagney <ac131313@cygnus.com> writes:
> > >> From: Jim Blandy <jimb@zwingli.cygnus.com>
> > >> Date: 11 Oct 2001 14:46:09 -0500
> > >>
> > >> You have have missed it, but this is a patch to gdb/doc/Makefile.in.
> > >
> > >
> > > I didn't miss it, it's just that I never use texi2html (and frankly
> > > don't understand why won't we use "makeinfo --html"), and Andrew
> > > already gave his blessing.
> >
> > From memory, at the time texi2html gave better output than `makeinfo
> > --html` (why it was better I don't remember). It is probably getting
> > near high time to re-consider the decision.
>
> >From gdb/doc/Makefile.in:
>
> # Note that texinfo 4.0's makeinfo --html can only generate a
> # single file, which would be too large, so continue to use
> # texi2html. -sts 2000-03-28
March 2000? That's ages ago ;-)
Anyway, there are versions of Texinfo on alpha.gnu.org which support
split by node. Also, I have a small program I wrote years ago which
can split an HTML file produced by makeinfo by nodes (and rewrite all
the xrefs, so they stay valid).
texi2html has a problem that it doesn't support all the latest
additions to Texinfo, so using it will put a drag on us when we will
want to use those new features. (Did someone see what do @ifnothtml
and @ifnottex do in texi2html?)
next prev parent reply other threads:[~2001-10-11 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <npbsjedkou.fsf@zwingli.cygnus.com>
2001-10-11 15:17 ` Eli Zaretskii
2001-10-11 15:32 ` Andrew Cagney
2001-10-11 17:17 ` Jim Blandy
2001-10-11 23:39 ` Eli Zaretskii [this message]
2001-10-12 13:52 ` Jim Blandy
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=5567-Fri12Oct2001083936+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zwingli.cygnus.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