According to Michael Olds:
> For general information: this is how, apparently, a person who does not host
> their own website is hooked up to ht:/Dig:
>
> GD: The important questions are, what is the value of "config" in your
> search
> form, and what is the value of "CONFIG_DIR" in your source tree's CONFIG
> file? If CONFIG_DIR is something other than /home/I/the/user/htdig,
> where your htdig.conf file is, or if the search form's setting of the
> "config" input parameter is not "htdig", then htsearch will not use your
> /home/I/the/user/htdig/htdig.conf file and will not see the changes you
> made to it
>
> Response by my host:
> CONFIG_DIR is set to /usr/local/web/htdig/conf. In that directory,
> user.conf is symbolically linked (like an alias or shortcut) to
> ~user/htdig/htdig.conf. Changes to that config file are effective
OK, that means that each user can only have one single config file. So,
in your case, a config=mikeolds input parameter to htsearch will select
/usr/local/web/htdig/conf/mikeolds.conf, which is a symbolic link to
~mikeolds/htdig/htdig.conf, so that is the one and only config file you
can use for htsearch on this system.
> On the version made available to me, the word is:
>
> The version of htdig installed on our server does not have the
> start_highlight and end_highlight attributes.
>
> Is this reasonable? In any case I have requested a list of which attributes
> are available.
Apparently, the htsearch version on your site is 3.1.0b2, which is pretty
ancient. You will be lacking a lot of recent features and bug fixes. Most
notably, start_highlight & end_highlight which were added in 3.1.4, and
extra_word_characters which was added in 3.1.2. You should refer your ISP
to http://www.htdig.org/RELEASE.html and point out all the changes since
3.1.0b2, especially a very important security fix in 3.1.5, and suggest they
upgrade.
> Meanwhile, I do not want to be pushy about this, but if it has been
> forgotten, I need to revive it, it is a vital aspect of my ability to use
> ht://Dig on my site:
>
> I checked back on my original correspondence and at that point it was
> indicated that this would not be a big problem using the
> extra_word_characters attribute. But I need to understand how to implement
> this. Simply placing these extra characters in the list is not going to help
> me. My users do not use these characters to search for the words. Again,
> back at the original correspondence about this the thought was that "...I
> would guess that you'd want to work out a mapping using the "accent" fuzzy
> match, including for your convention."
> I just finished a frustrating look-see at the ht/dig site and at the source
> forge link I was given earlier for this "accent" fuzzy match thing, and came
> up with nothing.
Well, without 3.1.2 or later, you won't have extra_word_characters.
Also, the "accents" fuzzy algorithm is available as a patch to 3.1.5,
so your ISP would need to upgrade to 3.1.5 and add the accents.5 patch
from ftp.ccsf.org to get this feature working for you. Finally, as
I mentioned in a message yesterday, the accents algorithm currently
supports only ISO-8859-1 (Latin 1) accents, so you'd either need to
customize the mapping table in the patch, or you'd need to re-encode
your fonts and documents to support a character set with compatible
positions for accented letters. E.g., an accented "a" would have to go
in the slot for a Latin 1 accented "a" of one form or other, and so on.
The accents fuzzy algorithm will be in 3.1.6, whenever we get it out,
so if your ISP will support this, and you recode your fonts, this may get
searches working for you with these documents. I can't promise anything
about adding extra_word_casemap and accents_map to 3.1.6 - it'll be an
effort just to get the existing patches committed and documented for this.
--
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
