I don't use 5.01.065 anymore, I know we had some issues, but I don't
remember the extent. I do remember having to write most of our
webservices in RealBasic, and bypass witango alltogether. It wasn't
until 5.5 that we were able to get around these encoding issues, and
use witango with these types of characters. Don't misunderstand, 5.5
is still a bear with these types of characters, but it can be done.
If my memory serves me, we gave up on it with 5.01.065.
If you plan on staying with witango, I would seriously recommend
moving to 5.5, what is the bug in directDBMS you are dealing with?
There may be a workaround.
--
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 Jun 13, 2006, at 2:30 AM, Francis Lebourq wrote:
De : William M Conlon <[EMAIL PROTECTED]>
I don't think the accented characters are in the iso-8859-1
character set. Have you tried utf-8 encoding?
The accented characters like éèà... are in the iso-8859-1 character
set. The exception is the € sign (include in the iso-8859-15
character set)
De : Robert Garcia <[EMAIL PROTECTED]>
What version of witango server are you using?
I use witango server 5.0.1.065 on Mac OS X.
and i cannot use 5.5 version. There is a bug with Direct DBMS
action (i have reported this on this list and on Witango support)
How are these characters getting into your xml, are they coming
out of a DB, or from a form?
It's a "quick and dirty" test directly in .taf file (copy in
attachment). No DB, no form,...
Unfortunately, witango does not support anything but ISO-8859-1
but should work with these characters.
Yes and the final goal is to write a file in ISO-8859-1.
De : Ben Johansen <[EMAIL PROTECTED]>
but it looks like he is inserting a second header into an already
established DOM
<xml version="1.0" encoding="iso-8859-1" standalone="no">
I have tested with this header to "force" iso-8859-1 character set.
But no change...
De : Robert Garcia <[EMAIL PROTECTED]>
try this:
<@dominsert local$thexml xpath="/root/whatever"><@replace
str='<@var local$mynewxmlstring>' findstr='<\?.+\?>' replacestr=''
type=regex></@dominsert>
I have tested this regex but no change...
Can you test my little .taf and tell me if this problem come from
witango on Mac OS X ?
I ask this because il have get another bug (only on Mac OS X...)
with accented characters in parameters path to a .tcf file. (i have
reported this on this list and on Witango support...)
Regards
Francis LEBOURQ
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
<Parse_xml.taf>
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
