Hi Erling, On Wed, 17 Dec 2003, Erling D. Andersen wrote:
> Hi, > > By the way I get dvips from the latest fptex for Windows. > > >Can you reply to this email, including the lines that dvips > >prints when it first starts up. > >In a terminal, or DOS window, or whatever, please try: > > dvips --help or dvips -help or dvips -h > > dvips --version or dvips -version or dvips -v > >or whatever else might reveal the startup message. > >Try several, in case the responses are different. > > Here are > > C:\>dvis -v > 'dvis' is not recognized as an internal or external command, > operable program or batch file. That's a mis-typing; result as expected. > > C:\>dvips -v > This is dvips(k) 5.94a Copyright 2003 Radical Eye Software (www.radicaleye.com) This is what we want to use, I'd expect. > > C:\>dvips --version > dvips(k) 5.94a > kpathsea version 3.5.2 > Copyright (C) 2003 Radical Eye Software. > There is NO warranty. You may redistribute this software > under the terms of the GNU General Public License > and the Dvips copyright. > For more information about these matters, see the files > named COPYING and dvips.h. > Primary author of Dvips: T. Rokicki; -k maintainer: T. Kacvinsky/ S. Rahtz. A much longer version; fine. > > C:\> > > >So to check what is happening, can you please add some print lines: > > > >> foreach $veropt (@tryopts) { > >> my ($stat,$msg,$err) = &get_out_err("$dvips $veropt"); > >> > >> $msg .= $err || ''; > > > >print "\nSTAT:$stat, MSG=$msg"; > >> > >> if(!$stat && $msg =~ /(?:^| )dvips(?:\(k\)|k|)\s*(\d+[.]?\d*[A-Z]?)/is) { > >> $version = $1; > >print "; VERSION=$version\n"; > >> last; > >> } > >> } > >> > > Ross note that > > C:\Program Files\TeXLive\bin\win32\dvips.exe > > i.e. it contain a space in path. Can it cause problems. The output you ask for is > below. > > Warning: Will not automatically install LaTeX2HTML style files. > checking for dvips... C:\Program Files\TeXLive\bin\win32\dvips.exe > checking dvips version... > STAT:1, MSG=This is dvips(k) 5.94a Copyright 2003 Radical Eye Software (www.ra > caleye.com) > Missing DVI file argument (or -f). > Try --help for more information. > STAT:1, MSG='C:\Program' is not recognized as an internal or external command, > operable program or batch file. > STAT:1, MSG='C:\Program' is not recognized as an internal or external command, > operable program or batch file. > STAT:1, MSG='C:\Program' is not recognized as an internal or external command, > operable program or batch file. Note how all of these return a $stat of 1 . So the reg-exp is never tested. The first one succeeds, sort of. If it had a $stat of 0 then it would be used to get the version. To find out exactly what command is being tested, put another `print' statement: > >> foreach $veropt (@tryopts) { print "\nCMD: $dvips $veropt "; > >> my ($stat,$msg,$err) = &get_out_err("$dvips $veropt"); I suspect that it is *not* dvips -v so to fix the problem nicely, the commands to be tested should include this as one option. Preferably quite early in the list. > C:\Program Files\TeXLive\bin\win32\dvips.exe > > i.e. it contain a space in path. Can it cause problems. The output you ask for is > below. Yes. This could be why the 2nd, 3rd and 4th tests fail. Hope this helps, Ross > > Erling > > > **************************************************************************** > Denne mail er blevet scannet af http://www.virus112.com > **************************************************************************** > _______________________________________________ > latex2html mailing list > [EMAIL PROTECTED] > http://tug.org/mailman/listinfo/latex2html > _______________________________________________ latex2html mailing list [EMAIL PROTECTED] http://tug.org/mailman/listinfo/latex2html