Greetings Gilles, In htcommon/defaults.cc, startyear is specified as 1970, so your config file would have to explicitly clear startyear to say no date is given.
The reason for startyear being specified in defaults.cc is that the default value should be in attrs.html, which is automatically generated. The three fixes I can think of (in order of my preference) are: 1. Set the (hard-coded) default value of startday in htsearch/Display.cc to 0 instead of 1. I'm not sure if this would work, and it may break other things. 2. Leave startyear empty in defaults.cc and manually hack attrs.hml. 3. Leave startyear undocumented. Opinions? Cheers, Lachlan On Wed, 22 Oct 2003 08:30, Gilles Detillieux wrote: > even > though these dozen or so web pages were definitely in the database, > and came out into db.docs after an htdump (with a m:0 field), > htsearch would not show these in search results. I looked at the > code, and the only thing that I can see that would cause this is if > the startyear, startmonth or startday input parameters were set, > causing the timet_startdate value in Display.cc to be greater than > 0. But I didn't set these! I ran htsearch from the command line, > so I know I wasn't passing it these values as input parameters, and > the config file I used didn't define these as attributes either. -- [EMAIL PROTECTED] ht://Dig developer DownUnder (http://www.htdig.org) ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
