It can happen that the web browser either does not support UTF-8 for Ajax calls, or that you have not set the Ajax call to accept UTF-8 (In Firefox, for instance, I have not been able to set the actual encoding for Ajax calls, although it might be possible) (Note that setting the actual encoding is different from using an encoding description request header.)
The easiest way, if you want a fix, is to use an encode-uri function on the server and in the ajax javascript, then the transfer encoding will not matter. Regards Hans On 8/30/06, Binkley, Peter <[EMAIL PROTECTED]> wrote:
I'm updating an old Cforms project from 2.1.7 to 2.1.9 and adding Ajax. The setup is similar to the form1.flow sample, where the uploaded form is sent to a pipeline that starts with a jx template. I've set things up so form fields are interpreted as UTF-8. Everything works under 2.1.9 if I don't turn Ajax on (with "ajax=true" in the form template). If I do turn ajax on, though, any accented characters I type into a form field end up as question marks in the output. It appears that turning ajax on causes the form handling to be done in ISO-8859-1 instead of UTF-8. Has anyone else seen this, and is there a known fix? Thanks, Peter Peter Binkley Digital Initiatives Technology Librarian Information Technology Services 4-30 Cameron Library University of Alberta Libraries Edmonton, Alberta Canada T6G 2J8 Phone: (780) 492-3743 Fax: (780) 492-9243 e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
