Comments on: Bashpodder and Poorly-Written XML Files… http://blogs.oldradio.net/archives/2005/11/07/bashpodder-and-poorly-written-xml-files/ Ramblings of an Old Man on Old-Time and Contemporary Radio, Television, the Arts, and the News; includes OTR Podcast Sun, 7 Sep 2008 02:37:34 +0000 http://wordpress.org/?v=2.0.4 by: RD http://blogs.oldradio.net/archives/2005/11/07/bashpodder-and-poorly-written-xml-files/#comment-1477 Sun, 13 Nov 2005 23:14:56 +0000 http://blogs.oldradio.net/archives/2005/11/07/bashpodder-and-poorly-written-xml-files/#comment-1477 I have not seen the particular XML files of which you speak. However, I am somewhat of an XML expert (I have written three XML courses, and I work with XML in several different contexts) and I suspect you are placing blame in the wrong place. There is no need for carriage returns/linefeeds in "properly" written XML files. To an XML parser, the tags are what define elements, not carriage returns. <em>Yes, yes, the containers are what define the elements (the same is true in HTML, and every other hypertext language I know of), and bashpodder should process the stream instead of the lines. That said, it's pretty stupid not to have returns (or line feeds, I'm catholic on line terminators) to seperate the objects, if for no other reason than clarity. When the preponderance of files contain them, and the rarity is that which does not, it's reasonable if not technical to suggest the rarity is not "proper." --cfs3</em> I have not seen the particular XML files of which you speak. However, I am somewhat of an XML expert (I have written three XML courses, and I work with XML in several different contexts) and I suspect you are placing blame in the wrong place. There is no need for carriage returns/linefeeds in “properly” written XML files. To an XML parser, the tags are what define elements, not carriage returns.

Yes, yes, the containers are what define the elements (the same is true in HTML, and every other hypertext language I know of), and bashpodder should process the stream instead of the lines. That said, it’s pretty stupid not to have returns (or line feeds, I’m catholic on line terminators) to seperate the objects, if for no other reason than clarity. When the preponderance of files contain them, and the rarity is that which does not, it’s reasonable if not technical to suggest the rarity is not “proper.” –cfs3

]]>