On Fri, May 10, 2002 at 10:36:50AM +0200, Bernd Eidenschink wrote: > So far, the 3.4.2 version features the undocumented parameters: > > ns_section "ns/encodings" > ns_param adp iso8859-1 > > in the config.
I couldn't make any sense of the ChangeLog for AOLserver 3.4; it wasn't clear what the encoding support did and, as you note, documentation was lacking. Furthermore, the changes didn't seem to cover [ns_getform], and we had trouble before with non-ascii characters submitted through html <form>'s. I chose to back out 3.4's limited encoding support and fold the +ad13 encoding changes back in, not the least because of Rob's documentation in encoding-doc.html . > 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? My own. I don't have write access to the Sourceforge CVS. The most I can do is submit the patch, but that's not one I expect to see folded into the main release since the 4.x snapshot has its own encoding support. > 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... I noticed that 4.x keeps one encoding per struct Conn while +ad13 keeps one for pages and one for form data. Other than that, the coverage looks similar --but I haven't tried it yet. Hmmm, the documentation still seems a little thin. > And supporting ONLY UTF-8 - as > encoding both of the webserver AND the DB - is also not always the best > solution for many people. Rob's file says that the DB has to be UTF-8. On the webserver side he gives instructions for other encodings, I haven't had the time to try them either.
