On 8/3/07, Stephen Deasey <[EMAIL PROTECTED]> wrote:
> The *.test file are in utf-8, and are sourced by Tcl, and I think Tcl
> it's picking up the default encoding to use from the env. So no real
> surprise there. You'd expect encoding.test:1.1, which is completely
> defined within that file, to fail.
>
> But why are the ADP tests failing? The ADP's should be read off disk
> in the correct encoding (and they seem to be). Tracing through the
> rest of it, the server seems to be spitting out the correct bytes (I
> think).
>
> So it's down to the test harness itself. It does this:
>
> proc nstest_http {args} {
> ns_parseargs {
> {-encoding "utf-8"} ...
> } $args
>
> ...
>
> #
> # Force a specific encoding (utf-8 default).
> #
>
> fconfigure $rfd -encoding $encoding
> fconfigure $wfd -encoding $encoding
>
>
> Which looks fair enough to me.
>
> Why isn't this working?
Well, I'm reasonably happy this is not a bug in the server but some
cruftyness in the test harness.
If you were relying on environment variables to set the Tcl system
encoding before, you'll want to use the new
ns/server/$server:systemencoding parameter.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
