Since there are several people on the htdig-dev list, I'd prefer to keep discussion on list. This also prevents duplication of effort in case someone else is thinking about doing similar work.
On Fri, 10 May 2002, Lachlan Andrew wrote: > On Thu, May 09, 2002 at 11:13:29PM -0500, Geoff Hutchison wrote: > > On Monday, May 6, 2002, at 08:51 PM, Lachlan Andrew wrote: > > >I'd like to help fix this problem ([413879] local files > > >and external parsers), to get searching back into the KDE > > >help centre. > > > > I'm not sure what problem you're referring to. Could you point me to a > > URL of the problem report? It's certainly not in the ht://Dig bug > > tracker at SourceForge. > > It's in the Feature Requests: > > >http://sourceforge.net/tracker/index.php?func=detail&aid=413879&group_id=4593&atid=354593 > > KDE help used to use ht://Dig to provide a search capability. > They changed the format of their files from HTML to docbook (XML). > For some reason, ht://Dig refuses to call the parser that one of > the KDE developers wrote. The response was that it was not a bug, > but a calculated feature, because ht://Dig didn't know that no server > parsing was necessary. > > It sounds like the simplest hack is just to add "docbook" to the > list of acceptable extensions (and get that into the CVS of course!). > However, the response suggested some more elegant solutions, which > I'll try... The best strategy depends on the version of ht://Dig you're intending to use. If you're only going to use 3.1.x versions for the near future, then yes, the hack you've mentioned is the best approach--add ".docbook" to the code in htdig/Document.cc::RetrieveLocal and the appropriate MIME type. For 3.2, the best approach is to either: a) Index using file:// URLs, which should use the appropriate mime.types file: <http://www.htdig.org/dev/htdig-3.2/attrs.html#mime_types> b) Code the RetrieveLocal method to produce temporary file:// URLs that are retrieved using the htnet/HtFile methods. (which again should use the appropriate mime.types file) The feature request is for option (b) and we'd certainly appreciate work in this direction. However, if you're looking for a workaround, in retrospect, I'd suggest using file:// URLs with 3.2 anyway. -- -Geoff Hutchison Williams Students Online http://wso.williams.edu/ _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
