Cheers Scott. Thanks again for the response. I guess the issue for me is I don't have control over the XML source, and when I heard u mention that Witango supported utf-8 then it sounded like what I was after to get out of this problem. Have u any more details on this? My data is already enclosed within the cdata section, so unfortunately this won't work.
Mike. -----Original Message----- From: Scott Cadillac [mailto:[EMAIL PROTECTED] Sent: 20 September 2005 14:16 To: [email protected] Subject: RE: Witango-Talk: support for @DOM encoding Hi Mike, > As for replacing the Euro symbol with the € equivalent, > surely this isn't a viable option considering the amount of > characters that may be used but not supported in the DOM variable? XML is strict. You can't be lazy with it like you can with HTML. If you want to use XML, you have to play by the rules. Entity encoding just happens to be an option available to you and is widely used. Fortunately some programming languages will automatically transform special characters within a string to entity equivalents for you, if you are writing to an XML type object (see C#). Unfortunately, some languages do not. Another option is CDATA sections, which may or may not help you in the case. Try surrounding your text with <![CDATA[ ...my text... ]]> or use ENCODING=CDATA Hope that helps. ~ Scott Cadillac ~ 403-254-5002 ~ [EMAIL PROTECTED] ~ Custom Software for Business http://custom.softwarefor.net ~ The XML-Extranet Partnership ~ P.O. Box 69006 RPO Bridlewood SW Calgary, Alberta Canada T2Y 4T9 > -----Original Message----- > From: Mike Scally [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 20, 2005 3:44 AM > To: [email protected] > Subject: RE: Witango-Talk: support for @DOM encoding > > Hi Folks, > > Thanks very much for your input/answers on this topic so far. > I am running Witango Server 5.5.009 and am having problems > with the encoding, so I'm not sure which version supports > UTF-8 encoding. > > I was hoping that as you suggested Scott, you could just set > the encoding type using <?xml version="1.0" encoding="UTF-8" ?> but to no avail. Is there anyone that has had any success > setting the encoding with the @DOM tag? > > As for replacing the Euro symbol with the € equivalent, > surely this isn't a viable option considering the amount of > characters that may be used but not supported in the DOM variable? > > Cheers > Mike. > > -----Original Message----- > From: Scott Cadillac [mailto:[EMAIL PROTECTED] > Sent: 19 September 2005 16:08 > To: [email protected] > Subject: RE: Witango-Talk: support for @DOM encoding > > Hi folks, > > By default Witango supports ISO-8859-1 character sets (basic > latin characters), but newer versions apparently support > UTF-8, which is more extensive. > > Note, I don't remember which version > introduced the UTF-8 support. > > In theory you should be able to just assign the encoding set > when your DOM variable is assigned, something like: > > <@ASSIGN local$myVar value="<@dom value='<?xml version="1.0" > encoding="UTF-8" ?><MyXml anAttribute="some characters" />'>"> > > So your success may depend on what version of Witango you are running. > > And as for encoding your character as € as your > alternative? This is standard XML practice - get used to it. > > Have a nice day :-) > > ~ Scott Cadillac > ~ 403-254-5002 > ~ [EMAIL PROTECTED] > > ~ Custom Software for Business > http://custom.softwarefor.net > > ~ The XML-Extranet Partnership > ~ P.O. Box 69006 > RPO Bridlewood SW > Calgary, Alberta > Canada T2Y 4T9 > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Monday, September 19, 2005 8:41 AM > > To: [email protected] > > Subject: Re: Witango-Talk: support for @DOM encoding > > > > I have the same problem since I have install Witango 5.5 > > Server. In prior versions it have work fine. > > One way for a work around: > > <@REPLACE STR="<@elementvalue object=user$allstringsdom > > element='root().id(Feld_@@local$Step)' encoding=none>" > > FINDSTR="?" REPLACESTR="€"> > > > > regards > > > > Daniel > > > > ----- Original Message ----- > > From: Mike Scally <mailto:[EMAIL PROTECTED]> > > To: [email protected] > > Sent: Monday, September 19, 2005 2:00 PM > > Subject: Witango-Talk: support for @DOM encoding > > > > > > Hi Folks, > > > > > > > > I wonder would anyone be able to tell me what character > > set the @DOM tag supports? > > > > > > > > I assign the Euro symbol (€) as part of the XML > > document using the @DOM tag, but when I read the value back > > out of the XML document it appears as a ? rather than the > > Euro symbol. This is causing me a bit of a problem and I am > > wondering if theres a way around it. Replacing the Euro > > symbol with the HTML equivalent € appears to be too > > complicated in my scenario. > > > > > > > > Thanks > > > > Mike. > > > > > > > > > > ******************************************************************** > > 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. > > > > ******************************************************************** > > <M<D< > > > > > > ______________________________________________________________ > > __________ > > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > > > ______________________________________________________________ > __________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > ******************************************************************** > 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. > ******************************************************************** > > ________________________________________________TOUNUBCRBE G > t htp//wwwiano.omdeelpe/milis.t > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ******************************************************************** 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. ********************************************************************
