STATUS of ht://Dig branch 3-2-x RELEASES: 3.2.0b2: Release date ?, Unfrozen 3.2.0b1: Released: 4 Feb 2000. SHOWSTOPPERS: KNOWN BUGS: * htdig/Image.cc doesn't use Transport classes. * URL.cc tries to parse malformed URLs (which causes further problems) (It should probably just set everything to empty) This relates to PR#348. * Not all htsearch input parameters are handled properly: PR#648. * If exact isn't specified in the search_algorithms, $(WORDS) is not set correctly: PR#650. (The documentation for 3.2.0b1 is updated, but can we fix this?) * Running on BSDI and similar systems causes coredumps because the regex code is incompatible. We need some sort of configure test for this. * SGML encoding/decoding does not work with numeric forms, e.g. " -> quote. * Modified database can cause problems with systems using the Berkeley db for other tasks (e.g. networking) PENDING FEATURES: * Hans-Peter's sort-by-url patch for htsearch * Creating a few simple httools: htpurge, htmerge, htnotify, htdump, htload, htstat TESTING: * ExternalTransport with non 'http' URLs. * URL parser * htfuzzy tests * New config parser * htmerge -m DOCUMENTATION: * Update cf_* pages to mention new config parser (i.e. URL-dependent config) * Add thorough documentation on htsearch restrict/exclude behavior (including | and regex). * require.html is not updated to list new features and disk space requirements of 3.2.x (e.g. phrase searching, regex matching, external parsers and transport methods, database compression.) * TODO.html has not been updated for current TODO list and completions. OTHER ISSUES: * Can htsearch actually search while an index is being created? * Can we reproduce the DB2 errors that sometimes cropped up in 3.1.x? (e.g. PR#473, PR#476) * Error messages should be more informative if no URLs are indexed by htdig or htmerge. PR#672. ------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this.
