From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Clint Adams <schizo@debian.org>, zsh-workers@sunsite.auc.dk
Subject: Re: build problem with new texi2html
Date: Mon, 19 Jun 2000 16:13:12 +0000 [thread overview]
Message-ID: <1000619161312.ZM14000@candle.brasslantern.com> (raw)
In-Reply-To: <20000619102518.A32081@scowler.net>
On Jun 19, 10:25am, Clint Adams wrote:
} Subject: build problem with new texi2html
}
} Seems that -expandinfo : use @ifinfo sections, not @iftex
} has changed to -expand [info,tex] : expand info/tex sections
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.
} did spew this:
}
} texi2html -expand info -split_chapter ./zsh.texi
} *** Duplicate node found: Files
} *** Duplicate node found: Description
} *** Duplicate node found: Description
} *** Duplicate node found: Description
(etc.)
Those are bogus warnings; they're duplicated subsection titles, not real
texinfo nodes. I.e., they're only duplicates because of the way the HTML
table-of-contents is created.
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.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-06-19 16:14 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 [this message]
2000-06-19 16:44 ` Clint Adams
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=1000619161312.ZM14000@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=schizo@debian.org \
--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).