RE: Witango-Talk: support for @DOM encoding

Wed, 21 Sep 2005 09:07:20 -0700

The latest beta build of the 5.5 server (012) that I’ve received  - it’s also running witango.com – contains:

 

“new libraries that provide better unicode support for the Europeans”

 

I have no clue if that might help you in this, or even what that might mean, but you should try to get an email to the WT guys to see. I can’t say when this build will be available, but I’ve been very happy with it.

 

Robert

 

From: Mike Scally [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 21, 2005 10:04 AM
To: [email protected]
Subject: RE: Witango-Talk: support for @DOM encoding

 

But surely doing a string replace is fixing 1 problem, when there can be numerous other characters supported for example in utf-8 that are going to cause similar problems at some stage that we may have not discovered yet? I have used the string replace myself as a stop gap, but I really don’t think it’s a solution as such.

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 21 September 2005 14:38
To: [email protected]
Subject: Re: Witango-Talk: support for @DOM encoding

 

Robert (and all on the list...),

 

as writen in a prev. Mail: This Bug (?) is comming up with the change to the new Witango 5.5 Server. In Version 5.0 Witango have handle the "€" sign correct.

 

The shortes way to make a workaround (for me) was to use the Witango:

 

<@Replace STR="yourtext_value" Findstring="?" Replacestr="€">

 

A better way will be, to replace the "€" sign directly on the insert command...

 

<@Replace STR="yourtext_value" Findstring="€" Replacestr="&euro;">

 

On this way you don't need any external or someting else. I have allready report the "€" Bug (and another UTF8 Problems) to With Enterprise and I'm sure, that Phil will fix it soon.

 

regards

 

Daniel

 

 

 

----- Original Message -----

Sent: Wednesday, September 21, 2005 3:06 PM

Subject: Re: Witango-Talk: support for @DOM encoding

 

I hope this comes out, so you can see in my email, but I just did a test with the cleaner.

 

First, the app. This app combines .NET and witango, because .NET allows me to control image uploads, and not allow over a certain size. So a form is passed to a .NET page, the .NET page accepts the form, and writes it out as a UTF-8 xml file, and saves the image, then redirects to witango, telling it the uid of the record, which is the name of the form and jpeg plus the extension.

 

I submit data with euros in it. The xml file still has the euros displayed properly, and in my app, I have it show me the witango ingested xml in a text area like this:

 

<TEXTAREA ROWS=5 COLS=60 WRAP=OFF NAME="">

<@var local$formxml type=text>

</TEXTAREA>

 

The text displayed after going through the cleaner, and being ingested into witango is this:

 

 

<form>

 

  <pr_date>9/15/2005</pr_date>

 

  <title>test euro €</title>

 

  <image_caption>test €</image_caption>

 

  <text>Here is antoher test €</text>

 

</form>

 

 

Hopefully, you see the Euros are in tact. Now here is how I parse this form into an array to insert into DB:

 

<@assign local$thexml '<@cipher action="">"decode" type="Base64" str="<@var local$resultset[2,1]>">'>

<@assign local$formxml <@dom "<@var local$thexml>">>

<@assign local$argnames <@elementname local$formxml xpath="/form/*">>

<@assign local$argvals <@elementvalue local$formxml xpath="/form/*">>

<@addrows local$theform <@transpose local$argvals>>

<@assign local$theform[0,*] <@transpose local$argnames>>

 

So above you see I check the xml dom to text, and euros are in tact, however, after parsing to the array, I check the arrays by outputing to text, and this is what I get (argnames, argvals, and theform):

 

pr_date

title

image_caption

text

 

9/15/2005

test euro ?

test ?

Here is antoher test ?

 

9/15/2005

test euro ?

test ?

Here is antoher test ?

 

 

So, some where in parsing the xml, witango loses the euros. I will test some more, this did not happen with my german text, but there were no euros present. I don't think it happens on assign, I am guessing it is a problem with the <@elementvalue> tag. Because I can see the xml text getting passed around fine.

 

Witango support: Is this a bug? or are we missing something.

-- 

 

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 21, 2005, at 5:09 AM, Robert Garcia wrote:

 

Send me your test xml, and I will try it.

 

-- 

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 21, 2005, at 2:46 AM, Mike Scally wrote:

 

 

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-----

From: Robert Garcia [mailto:[EMAIL PROTECTED]]

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:

 

 

 



********************************************************************
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.
********************************************************************

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

________________________________________________TOUNUBCRBE G t htp//wwwiano.omdeelpe/milis.t

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to