(BTW Henry, you're subscribed as rzepa, but this came from h.rzepa, thus
the posting problems.)
> The server we index has all the types set via the Apache mime.types,
> and -vvv correctly shows these as mapping to those in the htdig.conf
> file. An example of what (should) happen is at
> Having compiled 3.1.16 (using IRIX, we missed 3.1.15 out)
I think you mean 3.1.6 and 3.1.5.
> at all. The MIME types are all of the type chemical/foo. Might it be
> that somewhere hardcoded into htdig are the primary types, and
> chemical is not one of them?
Nope. We certainly don't hardcode such things and even if we did, I'm
pretty sure I'd make sure chemical/* was one of the possibilities.
> Can I ask if anyone has tested the external parsing calls, and if anyone
> has any suggestions as to what else we might try?
Certainly the external parsing and external converter calls have been
pretty thoroughly tested. One thing to keep in mind is that if an
extension is allowed by the htdig configuration, and an external parser
isn't set for that MIME, htdig will assume text/plain and index
It would help to see some of the htdig -vvv output to see what's happening
in more detail--is the external parser being called, is it somehow
expecting that it's an external converter, etc.
Williams Students Online