The docs say:

  AxOutputCharset
    Fix the output character set, rather than using either UTF-8
    or the user's preference from the Accept-Charset HTTP header.
    If this option is present, all output will occur in the chosen
    character set.

That sounds like it overrides any settings. I personally have been thinking that it overrides all settings as well.

===

While I haven't done any extensive testing, a couple of things caught my attention, so the rest of this email is FYI.

I noticed that when you use AxOutputCharset, the content_type of a response is set to html (AxKit.pm line 792):

  $r->content_type('text/html; charset=' . ($AxKit::Cfg->OutputCharset ||
"UTF-8"));

Wouldn't this be a problem if you were trying to send out, say, a plain-text output?

The other thing is that while trying to look for the culprit, I turned the check for $AxKit::Cfg->{output_charset_ok} in A::A::ConfigReader *off*, and immediately got a "use of wide characters in print..." error. Perl 5.8 seems to be real picky about this stuff... Since that was a direct result of my hacking around the code it may just be an accident but it still kinda worries me.

--d

Robin Berjon wrote:
Matt Sergeant wrote:

On Fri, 28 Feb 2003, Robin Berjon wrote:

Shouldn't AxOutputCharset override any previous setting?


Shouldn't XSLT encodings override any previous setting?


Doesn't AxOutputCharset runs last?




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to