Klaus Hofeditz ]project-open[ wrote:
I gave it a try since some of our users do upload files using tools
such as WINSCP. Since these files would also need to be accessible
through the ]project-open[ file manager, we need to come up
with a slightly more complex solution to detect files with
On Sunday, September 25, 2011 at 06:42 , Klaus Hofeditz ]project-open[ wrote:
Hi Guan,
- Show quoted message -
[encoding system] returns utf-8 just before running ns_returnfile 200
$type $file
If I set encoding system iso8859-1 before ns_returnfile 200 $type $file
tx everybody for the very useful input!
Using ns_returnfp is (for several reasons) not an option for us.
Recompiling tcl using
--with-encoding utf-8
did not resolve the problem. This time I used AOLserver 4.5.1 /
tcl8.5.10.
Just a guess here, but by default, TCL is compiled with Latin-1 encoding. This
causes some issues when you are trying to do certain things in utf-8, even if
you set all possible TCL config variables to use the UTF-8 charset. You could
attempt to recompile TCL with
--with-encoding utf-8
Howdy,
Looking at the code, ns_returnfile passes the filename through to the core
Ns_ConnReturnFile without any of the care that core Tcl does handling
filenames. You may be able to replace ns_returnfile with ns_returnfp, passing
a file handle returned from Tcl's open command which should be
Another thing you could do is to set tcl's default encoding to utf-8, so
that the filenames passed to Ns_ConnReturnFile are the same encoding as
what the core tcl commands do.
Set the default encoding with
encoding system utf-8
in some tcl file. It's possible this could have some side
