According to Michael Olds:
> Just to see if I understood the most basic aspect of this, I added
> formatting attributes to the Highlights in the config file: This is what I
> did:
>
>
> # Bad Word List. Words which should be excluded from searches.
> #
> bad_word_list: /home/bl/a/blabla_ablablablaka?/htdig/bad_words.txt
>
> # Format Highlight (Start and end highlight) (the searched for word is
> highlighted)
> # (always terminate)
> start_highlight: <font color="#CC6600">
> #
> end_highlight: </font>
>
> The spaces between the : and the <value> are 1 tab stop as that was what was
> done, apparently, in the example. I also tried spaces; this was done in
> "Text Pad" a text editor.
>
> I saved the file and uploaded using "overwrite"; did a search, and there was
> no change from the default black boldface
>
> Is there some kind of "refresh" needed to be done before such changes take
> place?
The format is correct, but are you sure you overwrote the correct
config file? Is this the config file referred to by the "config" input
parameter in your search form, and is it located in the same directory
as is compiled into htsearch by the CONFIG_DIR makefile variable in your
CONFIG file in the source directory?
E.g., in my htdig-3.1.5 source directory, the CONFIG file defines
CONFIG_DIR as "/etc/htdig", and my search.html form defines config as
"scrc", so the correct config file for my site is /etc/htdig/scrc.conf,
in which I have the following:
start_highlight: <font color="#900099">
end_highlight: </font>
The leading spaces or tabs after the colon are stripped out by htsearch's
attribute reading code.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
