From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
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: Fri, 12 Oct 2001 13:52:00 -0000 [thread overview]
Message-ID: <nppu7sbmx1.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <5567-Fri12Oct2001083936+0200-eliz@is.elta.co.il>
"Eli Zaretskii" <eliz@is.elta.co.il> writes:
> > >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 ;-)
Yep. But 4.0 is still the latest released version. :(
> 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).
Wow!
> 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?)
Oh, texi2html is a total mess. Code to handle -glossary is actually
present in the code, but I couldn't follow the logic far enough to see
why it didn't work.
I'd much rather use makeinfo, if it behaves acceptably.
If you know the folks maintaining texinfo, is there any chance you
could prompt them to look over the patch I sent them last week?
prev parent reply other threads:[~2001-10-12 13:52 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
2001-10-12 13:52 ` Jim Blandy [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=nppu7sbmx1.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.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