(The following is a message I sent to Zoran off-list, but I figured
folks from the list might already know the answer, so I'm sending it to
the list as well.)
Zoran,
Here's a reproducible example of what I'm talking about:
wats:nscp 75 encoding system
iso8859-1
wats:nscp 76 set u
On 2002.11.18, Steve Manning [EMAIL PROTECTED] wrote:
I'd be interested to understand how your running Wikit on AOLServer.
Just last Friday I installed it on our intranet but its running as cgi
with tclkit and a shell script launcher.
I'm doing something very similar, running it as a CGI with
Another interesting behavior:
wats:nscp 20 encoding system
utf-8
wats:nscp 21 set u
¾ÆÆ®¹Ìµð¾î
wats:nscp 22 set m
¾ÃƮ¹̵ð¾î
wats:nscp 23 string compare $u $m
0
Not what I would have expected.
-- Dossy
On 2002.11.22, Dossy [EMAIL PROTECTED] wrote:
(The
+-- On Nov 22, Dossy said:
Any idea what I'm doing wrong?
You're typing iso8859-1 into nscp. nscp doesn't use a Tcl channel for
input, so it does no charset translation on that input. Hence the system
encoding is irrelevant. You must only send UTF-8 to nscp, and you'll
only get UTF-8
Thanks a lot, Kieth. I thought that you have used EXTERNAL driver working,
that's the reason I tried. Let me try the INTERNAL driver now - I have
already compiled it.
Thanks,
-Durga
-Original Message-
From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On Behalf
Of Keith Paskett
Sent:
On 2002.11.22, Rob Mayoff [EMAIL PROTECTED] wrote:
+-- On Nov 22, Dossy said:
Any idea what I'm doing wrong?
You're typing iso8859-1 into nscp. nscp doesn't use a Tcl channel for
input, so it does no charset translation on that input. Hence the system
encoding is irrelevant. You
+-- On Nov 22, Dossy said:
This doesn't make sense. How do you explain this:
[deletia]
$u is getting set to what I'd expect it to, but $m isn't.
Tcl stores strings internally in UTF-8. Sometimes it converts strings to
UCS-16 (16-bit characters), for example to do regexp matching, and
On Friday 22 November 2002 16:38, you wrote:
Any idea what I'm doing wrong?
I will double-check this here but I have to agree with Rob.
The ncp channel is NOT encoding-aware. You should not
interpret (test/make_conclusion/etc) based on typing into
the ncp alone. I have an encoding-aware
In a message dated 11/22/2002 11:26:08 AM Eastern Standard Time, [EMAIL PROTECTED] writes:
Any idea what I'm doing wrong?
I will double-check this here but I have to agree with Rob.
The ncp channel is NOT encoding-aware. You should not
interpret (test/make_conclusion/etc) based on typing into
In a message dated 11/22/2002 11:22:20 AM Eastern Standard Time, [EMAIL PROTECTED] writes:
BTW, this is exactly the same problem that I described in
http://dqd.com/~mayoff/encoding-doc.html two years ago.
...which, btw, is the guide I used add encoding support to aolserver 3.4 and 4.0. It's a
In a message dated 11/22/02 11:36:17 AM Eastern Standard Time, [EMAIL PROTECTED] writes:
Agree - it's nscp's very simple read code which eval's strings directly without converting to utf8. I suppose we could assume latin1 input and convert to utf8 or perhaps provide a command to set the nscp
Keith,
It works geat!!..I re-configured the AOL web server to look at Internal
driver (iusid.so). Right now, I am able to access the data from Informix
database. I have a question, though. Can I use all ns_** functions that
provided by AOL web server? I have a error message when I tried to use
The ncp channel is NOT encoding-aware. You should not
Agree - it's nscp's very simple read code which eval's strings
directly without converting to utf8. I suppose we could assume
latin1 input and convert to utf8 or perhaps provide a command to
set the nscp encoding.
Tcl has APIs for this
Dossy
Thanks for that. I'll leave it running on Wikit out of cgi then. I'm
sure our developers on an intranet aren't loading up the server as much
as your public one or the tclers wiki so I dare say it'll survive. I'd
recommend anyone with a bunch of developers to stick a wiki on an
intranet. The
|
|Keith,
|
|It works geat!!..I re-configured the AOL web server to look at Internal
|driver (iusid.so). Right now, I am able to access the data from Informix
|database. I have a question, though. Can I use all ns_** functions that
|provided by AOL web server? I have a error message when I tried
On 2002.11.22, Steve Manning [EMAIL PROTECTED] wrote:
By the way I couldn't find the AOLServer Wiki mentioned on the AOLServer
site. Am I being blind or has is disappeared?
It disappeared. It /used/ to be on the very first page, at
http://aolserver.com/ ... then it went away.
-- Dossy
--
Everyone,
After thorough testing, I've finally committed the changes to
nsvhr and nsunix which originated from Jerry Asher's excellent
work on these two modules for the AOLserver 3.3.x core, which
I reviewed and pared down to the minimal changes and have
tested against the AOLserver 3.5.x core.
17 matches
Mail list logo
