According to Chad M. Stewart:
> I think it would help if the examples in the documentation had explanations 
> as to what the examples are trying to accomplish.
> 
>  From the url_part_aliases doc it says
> 
> "A list of translations pairs from and to, used when accessing the 
> database. If a part of an URL matches with the from-string of each pair, it 
> will be translated into the to-string just before writing the URL to the 
> database, and translated back just after reading it from the database."
> 
> url_part_aliases:     http://mgate/ http://balius.com/
> 
> I indexed using no url_part_aliases and put the above in the htdig.conf 
> file for the search to read.  I got back URLs that begin with http://mgate/
> 
> What am I not understanding here?  I can architect a mail system to support 
> 1M users easily and yet this stupid thing has me stumped. :)

As far as I can tell, you're trying to get by with a single definition of
url_part_aliases, something the documentation, and especially FAQ 4.17,
are quite explicit in stating doesn't work.

The last part of the description of url_part_aliases (the part that begins
with a bold "Please note") does explain the example, at least the part
about needing a different url_part_aliases setting in htsearch than for
the other programs in order to do URL rewriting.  The right hand string
in each pair (the "to" string) is an arbitrary internal encoding of a part
of the URL, which is converted back the the left hand string by htsearch.
It MUST be a two stage process - that's how url_part_aliases was designed
to work.

-- 
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

Reply via email to