Hi Pierre,
> > I wrote a document about this a while back when I tried to make it all
> > work at ArsDigita: <http://dqd.com/~mayoff/encoding-doc.html>. However,
> > the code examples in that document apply to the ArsDigita versions of
> > AOLserver (the last of which is 3.3+ad13). I hacked those versions to do
> > character set translations. Probably none of the example code will work
> > in the standard versions of AOLserver.
>
> I pulled the charset-related changes out of 3.3+ad13 and forward-ported
> them to 3.4.2, replacing the few charset tweaks introduced in AOLserver
> 3.4. The patch includes your document. Any takers?
>
> So far it seems to work for us. We only have to support UTF-8, but
> the patch fixed problems with form submission.
So far, the 3.4.2 version features the undocumented parameters:
ns_section "ns/encodings"
ns_param adp iso8859-1
in the config.
I cite Kriston Rehberg from a mail in this list (March):
"[...] 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."
You say to took Robs code and ported it to 3.4.2 -- did you do that for your
own version of AOLserver or did you commit it to the Sourceforge version?
It would be great to know that Robs code or smth. similar is going to be
implemented in 3.4.2 or 4.0 of the standard AOLserver release. This would
solve
so much problems. So far the "ns_param adp iso8859-1" seems to work most
of the day but you can never be sure... And supporting ONLY UTF-8 - as
encoding both of the webserver AND the DB - is also not always the best
solution for many people.
Kind Regards,
Bernd.
