Re: xml parsing escape characters

2005-01-21 Thread "Martin v. LÃwis"
Luis P. Mendes wrote: From your experience, do you think that if this wrong XML code could be meant to be read only by somekind of Microsoft parser, the error will not occur? This is very unlikely. MSXML would never do this incorrectly. Regards, Martin -- http://mail.python.org/mailman/listinfo/py

Re: xml parsing escape characters

2005-01-21 Thread Fredrik Lundh
Luis P. Mendes wrote: > xml producer writes the code in Windows platform and 'thinks' that every > client will read/parse the code with a specific Windows parser. Could > that (wrong) XML code parse correctly in that kind of specific Windows > client? not if it's an XML parser. > Do you know an

Re: xml parsing escape characters

2005-01-21 Thread Luis P. Mendes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ~From your experience, do you think that if this wrong XML code could be meant to be read only by somekind of Microsoft parser, the error will not occur? I'll try to explain: xml producer writes the code in Windows platform and 'thinks' that every clie

Re: xml parsing escape characters

2005-01-21 Thread Luis P. Mendes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ~From your experience, do you think that if this wrong XML code could be meant to be read only by somekind of Microsoft parser, the error will not occur? I'll try to explain: xml producer writes the code in Windows platform and 'thinks' that every clie

Re: xml parsing escape characters

2005-01-20 Thread Jeremy Bowers
On Thu, 20 Jan 2005 21:54:30 +0100, Martin v. LÃwis wrote: > Luis P. Mendes wrote: >> When I access the url via the Firefox browser and look into the source >> code, I also get: >> >> > xmlns="http"> ~ >> ~439 ~ >> >

Re: xml parsing escape characters

2005-01-20 Thread "Martin v. Löwis"
Luis P. Mendes wrote: When I access the url via the Firefox browser and look into the source code, I also get: ~ ~439 ~ Please do try to understand what you are seeing. This is crucial for understanding what happens. You may have the

Re: xml parsing escape characters

2005-01-20 Thread Luis P. Mendes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I would like to thank everyone for your answers, but I'm not seeing the light yet! When I access the url via the Firefox browser and look into the source code, I also get: ~ ~439 ~ should

Re: xml parsing escape characters

2005-01-20 Thread "Martin v. Löwis"
Irmen de Jong wrote: Usually, but not in this case. If you have a text that looks like XML, and you want to put it into an XML element, the XML file uses < and >. The XML parser unescapes that as < and >. However, it does not then consider the < and > as markup, and it shouldn't. That's also what

Re: xml parsing escape characters

2005-01-20 Thread Irmen de Jong
Martin v. Löwis wrote: Irmen de Jong wrote: The unescaping is usually done for you by the xml parser that you use. Usually, but not in this case. If you have a text that looks like XML, and you want to put it into an XML element, the XML file uses < and >. The XML parser unescapes that as < and >.

Re: xml parsing escape characters

2005-01-20 Thread "Martin v. Löwis"
Irmen de Jong wrote: The unescaping is usually done for you by the xml parser that you use. Usually, but not in this case. If you have a text that looks like XML, and you want to put it into an XML element, the XML file uses < and >. The XML parser unescapes that as < and >. However, it does not th

Re: xml parsing escape characters

2005-01-20 Thread "Martin v. Löwis"
Luis P. Mendes wrote: with:DataSetNode = stringNode.childNodes[0] print DataSetNode.toxml() I get: ~ ~439 ~ ___- so far so good, but when I issue the command: print D

Re: xml parsing escape characters

2005-01-20 Thread Kent Johnson
Irmen de Jong wrote: Kent Johnson wrote: [...] This is an XML document containing a single tag, , whose content is text containing entity-escaped XML. This is *not* an XML document containing tags , , , etc. All the behaviour you are seeing is a consequence of this. You need to unescape the co

Re: xml parsing escape characters

2005-01-20 Thread Irmen de Jong
Kent Johnson wrote: [...] This is an XML document containing a single tag, , whose content is text containing entity-escaped XML. This is *not* an XML document containing tags , , , etc. All the behaviour you are seeing is a consequence of this. You need to unescape the contents of the tag to

Re: xml parsing escape characters

2005-01-20 Thread Kent Johnson
Luis P. Mendes wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 this is the xml document: http://www..";> ~ ~ 439 (... others ...) ~ This is an XML document containing a single tag, , whose content is text containing en

Re: xml parsing escape characters

2005-01-20 Thread Luis P. Mendes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 this is the xml document: http://www..";> ~ ~ 439 (... others ...) ~ When I do: print xmldoc.toxml() it prints: http://www...";> ~ ~439

Re: xml parsing escape characters

2005-01-19 Thread "Martin v. Löwis"
Luis P. Mendes wrote: I get the following result: http://www..";> ~ Most likely, this result is correct, and your document really does contain I don't get any elements. But, if I access the same url via a browser, the result in the browser window is something like

xml parsing escape characters

2005-01-19 Thread Luis P. Mendes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I only know a little bit of xml and I'm trying to parse a xml document in order to save its elements in a file (dictionaries inside a list). When I access a url from python 2.3.3 running in Linux with the following lines: resposta = urllib.u