Re: [PATCH] URI query sep char instance vars

2002_12_27 [EMAIL PROTECTED] wrote: > Perhaps there is some filter on the way that > kills messages from him on the way to me. This message may suffer a similar fate, if that is the case. Fortunately, that won't be a significant loss as this may well be the last message in the thread... http:

Re: [PATCH] URI query sep char instance vars

2002_12_26 [EMAIL PROTECTED] wrote: > no provision for changing $default_query_sepchar > except changing the source. : > it is probably a good idea that's what I'd gathered from the feature request thread. > If it does later become allowed, perhaps it should > be handled by import() so it norma

[PATCH] URI query sep char instance vars (Was: libwww-perl-5.66)

2002_12_23 [EMAIL PROTECTED] wrote: > There were lots of mail in my libwww archives that I did > not find the time to go through this time. Some of > these probably contains patches that I should have > applied. If you think I forgot your patch please > consider resending it. actual patch: htt

Re: HTML::Tree -- encoding entities >255 -- conflict between parse() and as_HTML()

2002_12_16, [EMAIL PROTECTED] wrote: > to be able to round-trip a document that has "&lbar;" > (or whatever) in it, even tho that's not in the HTML DTD. The kludge I used does that, although it could be modified to be more careful and not do it. I only took that approach because it was easier t

Re: HTML::Tree -- encoding entities >255 -- conflict between parse() and as_HTML()

Dave Mitchell wrote: > strongly suggest you use Perl 5.8.0 Thanks :) I think I failed to express in my original email that I need for this work to in perl 5.6. I'm aware that this problem vanishes in later versions of perl and even quoted that exact section of the docs in a URL mentioned in

HTML::Tree -- encoding entities >255 -- conflict between parse() and as_HTML()

Before I do something kludgey or think too hard trying to find a solution what others might have already encountered and solved, i thought I'd drop a quick line here to see anyone here had run into this... When using HTML::Tree to parse HTML (using perl 5.6, HTML::Tree 3.11) enocoded HTML enti

[PATCH] query separator instance variables for http URI objects

request for URI query separator character instance variables: http:[EMAIL PROTECTED]/#04055 post and discussion of very rough patch to provide same: http:[EMAIL PROTECTED]/#04097 time passes until I get back to the issue tonight :) I think I've incorporated all of the suggestions: o

Re: [rough PATCH] for URI query_sepchar instance variables

20020920 [EMAIL PROTECTED] wrote: > The more I look at it the more I think ';' as a separator > in a URI query is a bad idea that shouldn't be encouraged. The reason ';' is advocated (and is the default in CGI.pm now) is that '&' needs to be escaped in HTML. So, if your separator is '&' and you

delimeter instance variable for scalarref object (Was: URI-1.22)

I've been off on vacation, then sick, but am now catching up on email and I saw this: 2002_09_03 [EMAIL PROTECTED] wrote: > How about an option to someway tell query_param to use > (if not default to) ";" as the separator in query strings > instead of "&"? 2002_09_03 [EMAIL PROTECTED] wrote: