According to Craig Wallace: > 5.21 in the FAQ says both ; and & (though it doesn't say & which would > be prefereable)
You can of course use & which should get translated to "&" by the web browser. No problems there. Even if for some reason it wasn't translated, and htsearch saw a raw "&" in the query string, it wouldn't care. As it allows both "&" and ";" as delimiters, it would simply see the word "amp" as a parameter with no value assigned to it, and ignore it. Again, no problem there. > can be used as a variable delimiter inthe next and previous > button links generated by htsearch, but where can this be configured? There's nothing to configure. htsearch will split up the query string whenever it sees either a "&" or a ";". Both will work, on _input_. As for what htsearch puts out as the URLs for page buttons, they will use only ";" as the separator, for HTML 4.0 compliance. There's no configuration option to make it generate non-compliant output. Period. If you think the FAQ says otherwise, I'd say you misread (and misquoted) it. Take a closer look. -- 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 sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ ht://Dig general mailing list: <[EMAIL PROTECTED]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
