Hi,
> tells UTF-8 to use two bytes, which means you lose!). So for AOLserver
3.x
> the only real way to handle this kind of thing is to use nsd76. There is
> something in 3.4.2 called "encodings" in the configuration to force the
> nsd8x (Tcl 8.x) UTF-8 encoder to Do The Right Thing with the
af
The advice I'm giving here is probably completely worthless to you, but
AOLserver 3.x does not handle Latin-1 character sets well when using nsd8x
(Tcl 8.x) so try using nsd76. It has something to do with the way any UTF-8
encoder interprets a character set. The quick explanation is that the 127
On Thu, 28 Feb 2002, Bernd Eidenschink wrote:
> Hi,
>
> I don't know how to set up a combination of the latest AOLserver,
> using the nsd8x Interpreter, and a Postgres 7.2 database, that allows
> me to safely work with a charset of iso8859-1. Please don't throw
> stones, I know this has been disc
Hi,
I don't know how to set up a combination of the latest AOLserver,
using the nsd8x Interpreter, and a Postgres 7.2 database, that allows
me to safely work with a charset of iso8859-1. Please don't throw
stones, I know this has been discussed very often ;-)
How to do it?
The problems I run in
