At 5:49 PM +0100 1/8/00, Markus Mohr wrote:
>open(CAT, "$parsecmd") || die "Hmmm. $parser doesn't want to be opened
>using pipe.\n";
>print "\n\nKommando: $parsecmd\n";
>
>
>but this shows up only at the third error:
>
>External parser error in line:
> URL: http://www.columbiagames.com/StrategyGames/abaloneandchifoumi.pdf
>External parser error in line:
> URL: http://www.columbiagames.com/StrategyGames/abaloneandchifoumi.pdf
>External parser error in line:Kommando: ./pdftotext -raw
>/tmp/htdext.1133 - |
> URL: http://www.columbiagames.com/StrategyGames/abaloneandchifoumi.pdf
Phooey, I remember there was something I wanted to get into the 3.1.4
release--I updated these error messages in 3.2.0 to be a bit more
specific about what was wrong.
I'd worry about "./pdftotext" as a command. I have no idea what the
working directory is likely to be when the code is calling the parser
and it's not necessarily going to have the binary in it.
Try just "pdftotext -raw"
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
