From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19862 invoked from network); 3 May 2000 12:20:25 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 3 May 2000 12:20:25 -0000 Received: (qmail 4362 invoked by alias); 3 May 2000 12:20:20 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11112 Received: (qmail 4348 invoked from network); 3 May 2000 12:20:20 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de) From: "Andrej Borsenkow" To: "ZSH workers mailing list" Subject: FW: The latest texi2html (1.62) problem Date: Wed, 3 May 2000 16:20:17 +0400 Message-ID: <000101bfb4f9$f169ea90$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 > -----Original Message----- > From: Olaf Bachmann [mailto:obachman@mathematik.uni-kl.de] > Sent: Wednesday, May 03, 2000 3:43 PM > To: Andrej Borsenkow > Cc: texi2html@mathematik.uni-kl.de > Subject: RE: The latest texi2html (1.62) problem > > > > > bor@itsrm2% gmake html > > > texi2html -expandinfo -split_chapter ./zsh.texi > > > Unknown option: -expandinfo > > > This is texi2html 1.62 > > > To convert a Texinfo file to HMTL: /tools/bin/texi2html > [options] file > > > where options can be: > > > -expand [info,tex] : expand info/tex sections > > > ................. > > > > > > > Looks, like it was silently changed when maintenance went > over to Olaf > > Bachmann. No trace in ChangeLog, but it was changed in 1.61 > already (but > > not in some beta version I downloaded from it's site > > http://www.mathematik.uni-kl.de/~obachman/Texi2html/ ). > > > > To texi2html maintainers - the change is (sigh) > incompatible. Any way to > > retain old option for compatibility? > > > I thought that we had assured this backward compatibility. But > apparently not. I'll fix it next week (I'm really bussy this week). > > Olaf > >