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 characters in US-ASCII appear as exactly the same single-byte codes in UTF-8 as they do in US-ASCII (and technically the same as the lower 127 bytes of ISO-8859-1, known also as Latin-1). When a UTF-8 encoder encounters characters in the upper 127 bytes, i.e., the eight bit is set, the encoder goes haywire and picks the completely incorrect code (usually the eighth bit 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 aforementioned eighth-bit-set bytes but you'd have to ask someone else precisely how that fixes this thing.
I should also mention on a related topic that the EUR character is almost certainly not going to work unless you choose and stick to the proper character set... Windows has its own codepage and ISO has these fake ISO-8859-15 and ISO-8859-0 character sets to try to handle EUR. People editting content in MS Windows are not going to use the same EUR code as people writing a Tcl script on Unix. Watch for that. Kris
