Hello.
I have the same problem here in Poland. I wrote a quickhack that does
the trick in C.
It creates ns_utf8 Tcl command which I use to convert from external to
utf and back. I use this way:
Instead of
set text [ns_queryget text]
I use
set text [ns_utf8 eu [ns_queryget text]]
Now it
This happens due to various factors. AOLserver didn't historically do
anything about character sets, but Tcl 8.1 (and later) assumes that
strings in memory are in UTF-8 and performs conversions at its
boundaries. AOLserver puts stuff in Tcl's memory without doing that
conversion.
And HTTP and
+-- On May 9, atfrost said:
Tedious stuff, eh? But I'm not convinced that this isn't a bug.
Oh, I'm sure it's a bug. I'm just saying that it's probably not
something easily solved, or something that can be solved simply by
implementing published standards.
As far as I can tell, the
The version of ns_write/ns_return that I wrote as a TclObj command returns
binary data without altering it. I don't know if or how this relates as I
haven't had any cause to work with any non-US/English stuff.
The module is at http://www.vorteon.com/download/
and the patch against aolserver 4
