What I meant was I can fix it on the Tcl side where I'm getting the data, but to make it universal and transparent to Tcl coders such as myself it would have to fixed in the C code of things like ns_urldecode and ns_getform. And I have neither the time nor the chops to take that on right now. So I am asking if anyone had that in mind to do it. If not, it could eventually prove to be a high enough priority for us as we move to more AJAX input, so we would revisit allocating some resources to it at that point.
-T. -----Original Message----- From: Nathan Folkman [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 06, 2006 9:49 AM To: AOLSERVER@LISTSERV.AOL.COM Subject: Re: [AOLSERVER] urldecoding unicode? [EMAIL PROTECTED] wrote: > I have some data urlencoded by JavaScript's escape function which is > turning a Unicode apostrophe into %u2019. AOLserver doesn't recognize > this. I can certainly fix this in specific locations, but to handle > this universally it seems it this would need to be be fixed in > ns_urldecode and/or ns_getform. Any plans to do such a thing? > > -Titi > > -- AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in > the email message. You can leave the Subject: field of your email blank. > Would you mind submitting a patch for this? Thanks! - n -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
