Re: Bug in org.apache.jetspeed.util.URIEncoder

2000-10-10 Thread Paul Hammant
Santiago, "" needs to be added to the list INVALID_CHARACTERS "" is correct both in Windows and Unix filenames. I don't know about MacIntosh, but the list is not for encoding URL parameters, but for encoding whole URLs to be used as filenames. I changed the last error found, namely "?" is

Re: Bug in org.apache.jetspeed.util.URIEncoder

2000-10-07 Thread Santiago Gala
AA Z wrote: Santiago, We also experienced problem with URIEncoder. The way the invalid charaters are being translated aparently is not kosha with Linux (I imagine unix of most every flavors), namely replacing these characters with: "#" + (int)source.charAt(0) + ";"; confuses the

Bug in org.apache.jetspeed.util.URIEncoder

2000-10-05 Thread Paul Hammant
"" needs to be added to the list INVALID_CHARACTERS static var. It is used in URLs to separate params on the query string (though I guess everyone knew that). I would have changed it in CVS myself, but ant fails to build at the moment.. - Paul H --

Re: Bug in org.apache.jetspeed.util.URIEncoder

2000-10-05 Thread Santiago Gala
Paul Hammant wrote: "" needs to be added to the list INVALID_CHARACTERS static var. It is used in URLs to separate params on the query string (though I guess everyone knew that). "" is correct both in Windows and Unix filenames. I don't know about MacIntosh, but the list is not for

Re: Bug in org.apache.jetspeed.util.URIEncoder

2000-10-05 Thread AA Z
Santiago, We also experienced problem with URIEncoder. The way the invalid charaters are being translated aparently is not kosha with Linux (I imagine unix of most every flavors), namely replacing these characters with: "#" + (int)source.charAt(0) + ";"; confuses the hell out of file system,