Apologies for my complete silence lately. I'm just swamped. I'll try to catch up and hopefully contribute to the meeting discussion in a bit. However, I feel the need to respond to this posting promptly...
According to Lachlan Andrew: > Greetings Dominique, > > Thanks for the feedback. > > For problem (1), also set "no_next_page_text: [page suivante]". (I'll > fix that to default to next_page_text in the next release...) Please don't. There's a reason for using a different attribute for the next page text on the _last_ search page. Sometimes you want the same text (as by default) even though it's not actually a link, but sometimes you want different text, different formatting, or to suppress it altogether. Ditto for no_prev_page_text on the first search page. If the docs don't clearly state the relationship between the two attributes, or the rationale for separate ones, then it's a doc problem. Killing off no_next_page_text and no_prev_page_text would break a lot of configurations, including the example htdig.conf installed by default from installdir (where the non-existant prev or next page "button" is suppressed). > For problem (2), the ht://Dig option is > "search_results_order" (without the final "s"). Also, try removing > the "*" after each of the paths. That is, use > > search_results_order: \ > * /fr/Actualites/Nouvelles/ /fr/Actualites/nouvelles > > If that doesn't work, please fill in a bug report on at > <http://sourceforge.net/tracker/?group_id=4593&atid=104593> > > I've got no idea about problem (3). It is probably a bug. Please > fill in bug report at the above URL. Feature request. See below. > Cheers, > Lachlan > > On Wed, 2 Jun 2004 12:50 am, Dominique Arpin wrote: > > > 1- I use this option in the config: > > next_page_text: [page suivante] > > > > It works for all the pages, but in the last page, I didn't have > > [page suivante] but I have [next]. > > > > 2- This options doesnt work: > > search_results_orders: * /fr/Actualites/Nouvelles/* > > /fr/actualites/nouvelles/* > > > > I want to put all the page in the "/fr/Actualites/Nouvelles/* and > > /fr/actualites/nouvelles/*" sections a the end of the search > > result, but it doesnt work... > > > > 3- I have a problem with the accent and plurials. > > > > If a search for "herbe" or "herbes", no problems. But, if the > > works have an accent, like "acouphène", htdig have a problem to > > find the plural. > > > > herbe: 136 results > > herbes: 136 results > > > > acouphène: 6 results > > acouphènes: 25 results > > > > > > search_algorithm: exact:1 endings:1 prefix:1 accent:1 > > synonyms:0,5 htsearch does not yet support chaining of fuzzy match algorithms, so the results of the accents algorithms don't have the endings algorithm applied to them (nor vice-versa). This would be a very useful addition, but perhaps a bit tricky to get right. See previous discussions of this at http://www.htdig.org/mail/2000/05/0429.html and http://www.htdig.org/htdig-dev/2000/08/0090.html as well as the whole discussion thread at http://www.mail-archive.com/[EMAIL PROTECTED]/msg02573.html -- 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 new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
