Re: Re: Re: Re: XML Headaches

2007-07-09 Thread David Bovill
On 09/07/07, Malte Brill <[EMAIL PROTECTED]> wrote: the text is UTF-8 encoded. It appears to be a BOM issue. BOM might be an acronym or abbreviation for: #Bergen Ocean Model#Bid-O-Matic#Bill of Materials#Board of Medicine#Book of Mormon#Bureau of Meteorology, Australia#Byte Order Mark#Body of M

Re: Re: Re: Re: XML Headaches

2007-07-09 Thread Malte Brill
Hi David, yes, the text is UTF-8 encoded. It appears to be a BOM issue. I received the following tip that appears to do the job: Instead of unidecode(uniencode(myXML,"UTF8"),"ANSII") for the whole XML data I have the following script now: -- Remove byte order mark from UTF8 text if cha

Re: Re: Re: re: XML Headaches

2007-07-09 Thread David Bovill
Is the text actually UTF8 encoded - saying that it contians an an accented e (é) - and reading docs / doing this by hand may be a bit error prone? The first thing I'd do is check the XML with a validator and make sure that works - before looking for bugs? I've got some documentation with links to

Re: Re: Re: re: XML Headaches

2007-07-08 Thread Malte Brill
Hi, first of all thanks for your time. It appears that the external does not play nicely with UTF-8 encoding. But there might still be me doing something wrong. However, it is a blocker for a project at the moment. I have created an attachment to bug 5215. http://quality.runrev.com/qacenter/

Re: Re: Re: XML headaches

2007-07-06 Thread Martin Blackman
According to a handy little book I own, 'XML - in easy steps', > is the standard way to represent '>' in node contents, so it should work. But it also mentions that you can use the unicode character code '&#nnn;' for non standard characters. I tried a simplified test here on Windows and > worked

Re: Re: Re: XML headaches

2007-07-06 Thread Andre Garzia
Malte, I think the XML External will have trouble if > is present anywhere, even as node content. > is not an XML Entity, I had that problem before too, you can try replacing the ampersands for &. This may move your software forwards while RunRev External Quality Ninjas work out what is happening

Re: Re: Re: XML headaches

2007-07-06 Thread Malte Brill
Thanks Ken, that´s what I was afraid of. Andre: The > is in the contents of the node, not in the Tag name. The whole thing is UTF8 encoded, so I do not see how the external should lose any char in the node contents. It appears that it doesn´t get along with mixed stuff in node contents (btw: i