Send me your test xml, and I will try it.
Robert,
I seem to be still having problems. I have a test
XML file created, very simple with just the symbol that’s causing me the
problem
<?xml version="1.0" encoding="utf-8"
?>
<result>Euro Symbol : €</result>
However, when I call the External action, and the
results are returned, <@ELEMENTVALUE OBJECT="mydom" SCOPE="local"
ELEMENT="root()" TYPE="text"> resturns "?" instead of my symbol. Any
thoughts?
-----Original Message-----
Sent: 21 September 2005 01:49
Subject: Re: Witango-Talk: support for @DOM
encoding
Posted the solution, a external command helper to
http://
www.bighead.net/tools/
It is called witango_xml_cleaner.
Let me if it works for you.
--
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
On Sep 20, 2005, at 10:34 AM, Mike Scally
wrote:
Hi Robert,
Good work - I'm following this with interest as
you seem to be doing
something similar to myself. For Point 1, yeah
I could set the
encoding
using the @DOM, but it seems to be
ignored.
Would it be possible to use some other XML
parser other than
Witango to
do this? Maybe that has a COM interface that
can be used through
Witango. I haven't had need to do this but
maybe is an option? What
are
you planning to do with the external command
tool and the XML document
so Witango can parse it correctly?
Mike.
-----Original Message-----
Sent: 20 September 2005 17:12
Subject: Re: Witango-Talk: support for @DOM
encoding
Updates to this thread after more
testing:
1. When adding xml to a dom like so:
<@assign local$mydom <@dom
value='<?xml version="1.0"
encoding="UTF-8"?><xml />'>>
Witango does not complain about the
declaration, however, it does
ignore, and just assumes ISO-8859-1 encoding.
This also applies to
using the <@include file> method.
However, if you do an insert of xml with a
declaration, like from a
file, it will complain, and thrown an error. So
if you use
<@dominsert> and I assume
<@domreplace>, the xml you insert, must not
have a declaration, it must be stripped, and
again, ISO-8859-1
encoding is assumed.
2. I have a project we are just finishing, that
accepts xml that was
generated from ASP .NET, and is UTF-8 encoded.
I don't have control
at this point to say, please encode as
ISO-8859-1 so witango will
interpret correctly. I just tested this app
with some special
characters, german and spanish, and witango
messed them up, as
expected.
So I am writing a helper (external command) for
witango that will
solve this problem, because I have to present
this solution on
Thursday.
--
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
______________________________________________________________________
__
********************************************************************
This message is intended only for the use of
the person(s) ("the
intended recipient(s)") to whom it is
addressed. It may contain
information which is privileged and
confidential within the meaning
of applicable law. If you are not the intended
recipient, please
contact the sender as soon as possible. The
views expressed in this
communication may not necessarily be the views
held by LGCSB (Local
Government Computer Services Board).
Any attachments have been checked by a virus
scanner and appear to
be clean. Please ensure that you also scan all
messages, as LGCSB
does not accept any liability for contamination
or damage to your
systems.
********************************************************************
______________________________________________________________________
__
________________________________________________________________________
********************************************************************
This message is intended only for the use of the
person(s) ("the intended
recipient(s)") to whom it is addressed. It may
contain information which is
privileged and confidential within the meaning of
applicable law. If you
are not the intended recipient, please contact
the sender as soon as
possible. The views expressed in this
communication may not necessarily
be the views held by LGCSB (Local Government
Computer Services Board).
Any attachments have been checked by a virus
scanner and appear to be
clean.
Please ensure that you also scan all messages, as
LGCSB does not accept
any liability for contamination or damage to your
systems.
********************************************************************
õõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõõDòTå5T%45$”$S¢vòFò‡GG¢ò÷wwrçv—Fævòæ6öÒöFWfVÆ÷W"öÖ–ÆÆ—7BçF`
