The actual solution here was _way_ simpler than I originally thought.
All I had to do was change how I was parsing the QUERY_STRING from:
split(/\&/,$ENV{'QUERY_STRING'});
to:
split(/[;\&]/,$ENV{'QUERY_STRING'});
doh! ;)
Brandon Bell wrote:
>
> Thanks for the feedback Edmond.
>
> I think the only solution is to hack the htdig code as you suggest
below and
> revert the separator back to the '&'.
>
> If I use CGI.pm Version 2.64, which apparently does allow for the
semicolon
> separator, I still have the problem that when HTML forms are submitted
the
> ampersand is used, but when next/prev page clicks are done from the
search
> results page the semicolon is used. Because of this inconsistency,
writing
> any wrapper seems next to impossible to handle both cases at the same
time.
------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
