According to Lachlan Andrew: > The htmerge.html documentation currently says > > Note: You must run htmerge separately on each of the databases > created by htdig before merging them together with this option. > This is because merging the two wordlists together requires > wordlists that have already been cleaned up by htmerge. > > Am I correct in thinking that this is a carry-over from 3.1.x, and is > no longer true?
Yup! Now, what I'm not sure of is whether you'd need to run htpurge on each of the databases before merging. I'd be inclined to think it wouldn't be strictly necessary, but maybe helpful if one db has obsolete entries that would conflict with valid entries in the other. I don't know if Geoff can give more insight in this, as he's the one who did a lot of the design of htpurge and htmerge for 3.2. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
