From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13419 invoked from network); 19 Jun 2000 16:44:50 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 19 Jun 2000 16:44:50 -0000 Received: (qmail 756 invoked by alias); 19 Jun 2000 16:44:41 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11994 Received: (qmail 747 invoked from network); 19 Jun 2000 16:44:39 -0000 Date: Mon, 19 Jun 2000 12:44:30 -0400 From: Clint Adams To: Bart Schaefer Cc: zsh-workers@sunsite.auc.dk Subject: Re: build problem with new texi2html Message-ID: <20000619124430.A32766@scowler.net> References: <20000619102518.A32081@scowler.net> <1000619161312.ZM14000@candle.brasslantern.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i 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. -

Approximate Matching

+

13.9.5 Approximate Matching

-
  • Approximate Matching +13.9.5 Approximate Matching