BÁRTHÁZI András wrote:
Randal,
BÁRTHÁZI> use CGI;
BÁRTHÁZI> set_url_encoding('utf-8');
BÁRTHÁZI> The problem is that "use CGI" automagically initializes the
parameters
BÁRTHÁZI> *before* I set the encoding of them, so set_url_encoding
will run too
BÁRTHÁZI> late.
Did I miss the memo where anythi
> "BÁRTHÁZI" == BÁRTHÁZI András <[EMAIL PROTECTED]> writes:
>> Did I miss the memo where anything outside the list of valid
>> URI characters needed to be hexified, hence there's no need
>> for such a URL encoding scheme? Where is this memo?
BÁRTHÁZI> Can you write it again with other words?
Hi,
I believe that the standard for URL's calls for always encoding in utf-8
but that all non-ascii bytes (bytes with the high bit set) are to be
further encoded using %xx hex notation. So the URL is always
transmitted as an ascii string, but is easily converted into a utf-8
string simply by c
Hi,
Randal L. Schwartz wrote:
"BÁRTHÁZI" == BÁRTHÁZI András <[EMAIL PROTECTED]> writes:
Did I miss the memo where anything outside the list of valid
URI characters needed to be hexified, hence there's no need
for such a URL encoding scheme? Where is this memo?
BÁRTHÁZI> Can you write it again wi
Randal,
BÁRTHÁZI> use CGI;
BÁRTHÁZI> set_url_encoding('utf-8');
BÁRTHÁZI> The problem is that "use CGI" automagically initializes the parameters
BÁRTHÁZI> *before* I set the encoding of them, so set_url_encoding will run too
BÁRTHÁZI> late.
Did I miss the memo where anything outside the list of val
> "BÁRTHÁZI" == BÁRTHÁZI András <[EMAIL PROTECTED]> writes:
BÁRTHÁZI> use CGI;
BÁRTHÁZI> set_url_encoding('utf-8');
BÁRTHÁZI> The problem is that "use CGI" automagically initializes the parameters
BÁRTHÁZI> *before* I set the encoding of them, so set_url_encoding will run too
BÁRTHÁZI> late.
Stevan,
Well once we have a proper "use", we should be able to set the encoding
at compile time. But until then, I see a few possible options:
I think, it would be nice to find another solution.
- setting the url encoding forces a re-encoding of any parameters
already encoded.
This means extra w
Andras,
Well once we have a proper "use", we should be able to set the encoding
at compile time. But until then, I see a few possible options:
- setting the url encoding forces a re-encoding of any parameters
already encoded.
This means extra work if you change the encoding, but it will only
h
