According to Tom Metro:
> > With 3.1.3 and later versions, the pdf_parser sort of disables
> > itself. If given a full pathname to acroread, htdig will try to see
> > if the file exists, and if not, it will only complain once and not
> > try again.
> Yes, I noticed that, but if you're running rundig from cron, one peep
> and you'll get an email. And you don't want to send everything to
> /dev/null as you want to see real errors.
>
> I would say that because the Acrobat parser is not an integral part of
> the ht://Dig package, if not found by configure, it should be disabled
> by default. Someone installing a parser later can make the appropriate
> settings in htdig.conf to enable it, just as they would with any other
> parser.
That's a good point. It should be easier to turn off pdf_parser,
but for now, the most effective way is to add .pdf to bad_extensions
(or exclude_urls - that works too). That also prevents unnessary fetching
of the files.
> Also, I think I read in a mailing list message (when I was trying to
> find out more about indexing PDF documents) that the acroread v.4
> problem was fixed via a shell script wrapper. Why not just distribute
> that, rather than modify the PDF.cc source to acomodate Adobe's bugs?
> PDF.cc is already invoking a shell to run acroread, so I don't think
> it would be much of a performance hit.
At the time, it seemed to me that a one-time fix to the source code and
docs was a lot easier than continually having to re-explain how to set
up this little wrapper (or always pointing folks to an FAQ entry). The
idea was that the fix would be automatic this way. As it turned out, it's
still unreliable, hence the need for an updated FAQ entry. In short, it
seemed like a good idea at the time.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You'll receive a message confirming the unsubscription.
