Try having the ajax front end, base64 the text before it gets to
witango, and have the DB decode the base64 on insert. I have spent
years working through text encoding issues, especially witango.
I think there is also a new version of the server, or maybe its in
020, there is a encode/decode utf8 in witango cipher tag. Check the
release notes. Haven't used it yet.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Sep 26, 2007, at 6:06 PM, Jason Schulz wrote:
We're running 5.5.0020, and having an issue with inserting UTF8
from an Ajax front end into the database via Witango.
Witango appears to be converting the double byte characters into
two Latin1 characters, which breaks things.
Does anyone have a way of handling this?
Thanks,
Jason.
WITH IMAGINATION
Planning, Implementation and Management of Web Applications
Level 1, 44 Miller Street North Sydney NSW Australia 2060
phone + 612 9929 9229 fax + 612 9460 4770
web - www.wi.com.au email - [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by ESVA, and is believed
to be clean.
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
