From: Clint Adams <schizo@debian.org>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: build problem with new texi2html
Date: Mon, 19 Jun 2000 12:44:30 -0400 [thread overview]
Message-ID: <20000619124430.A32766@scowler.net> (raw)
In-Reply-To: <1000619161312.ZM14000@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Mon, Jun 19, 2000 at 04:13:12PM +0000
> Yeah, we reported that to the makeinfo maintainers and they apologized and
> said it was supposed to have remained backwards-compatible. The variant
> without the space is going to return in a future patch release.
>
> I'm not sure what that means we should do about it; There's probably some
> kind of configure/make foo that could insert a space if one is needed.
Parse `texi2html -version' if we can identify the affected versions.
On the other hand, if they're bringing it back soon, it's probably
not worth the trouble.
> Hmm, however, I've never seen the HTML generated by 1.62.1; perhaps it has
> changed from using generated numbers as the name= part of the anchors and
> is trying to use the actual section titles? That'd be a big improvement
> in some respects, but would introduces multiple anchors with the same name.
Here's a unified diff of 3.1.9 with old texi2html versus today's CVS with
new (grepped for "Approximate Matching"). So I guess the answer is no.
-<H3><A NAME="SEC61" HREF="zsh_toc.html#TOC61">Approximate Matching</A></H3>
+<H3> 13.9.5 Approximate Matching </H3>
-<LI><A NAME="TOC61" HREF="zsh_13.html#SEC61">Approximate Matching</A>
+<A NAME="TOC61" HREF="zsh_13.html#SEC61">13.9.5 Approximate Matching</A>
prev parent reply other threads:[~2000-06-19 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 14:25 Clint Adams
2000-06-19 16:13 ` Bart Schaefer
2000-06-19 16:44 ` Clint Adams [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=20000619124430.A32766@scowler.net \
--to=schizo@debian.org \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).