Yes, when 020 came out, I did test it, still didn't work reliably. If
you included high byte chars, and did it, they still got messed up.
There is a possibility, that with more time, I could have gotten it to
work, but we had already started porting to php, and now that is done.
Also, even though witango added this quick feature, witango still is
poorly suited for working with UTF-8, this just helped somewhat.
--
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 Mar 5, 2008, at 9:41 AM, Robert Shubert wrote:
NOTE: the template you download from my site, uses UTF-8
declaration, but should be the above, ISO-8859-1. No matter what,
you can't get witango 5.5 to properly output UTF-8.
Robert,
An update done in 5.5.020 was to add a UTF-8 conversion to @CIPHER.
This:
<@CIPHER action=encode str=<@VAR xml_text_block> type=utf-8>
seems to work as advertised. I have a customer who is returning data
to Google using this encoding and it is being accepted normally. I
saw that you listed the version in your header as 5.5.009, so I’m
not sure that you’ve ever seen that command.
Robert
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
