Re: UTF-8 problems with CGI script

Stephen Collyer <[email protected]> writes:

>> While preparing for the 2.6 release I stumbled upon an obvious bug in
>> the callback handlers - i.e. SAX2 character parsers. They are
>> transcoding into ASCII by default, and I have not provided a way to
>> override that, so everything will get tossed.
>
> Right. That wouldn't explain why the parser only fails in a CGI
> script though, would it ? I seem to have no problems in a command
> line environment, though I'm baffled as to why.

Oh, sorry, I didn't see that it only fails in CGI...

That sounds very odd. That could mean some import ENV variables are
not being set by the CGI user (like LANG?).

>> Stephen, could you send an example file and a short program that
>> demonstrates the problem? That would make it even simpler for me to
>> test that things are working as they should.
>
> Sure. I'll put together an LWP based sending script, and a corresponding
> CGI script, together with a command line script that works OK.
>
> May be a day or two till I do it though.

sure, that would be great. I'll be back in India in a few days and
will have better computer time then.

Cheers,
jas.