Comments on: XML Parsing http://javablog.co.uk/2007/03/29/xml-parsing/ by Java coders, for Java coders Tue, 15 Nov 2011 21:34:57 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: anon_anon http://javablog.co.uk/2007/03/29/xml-parsing/comment-page-1/#comment-50335 anon_anon Sun, 16 Aug 2009 02:04:14 +0000 http://javablog.co.uk/2007/03/29/xml-parsing/#comment-50335 <p>Another promising XML processing model is vtd-xml http://vtd-xml.sf.net</p> <p>http://winslab.cnu.ac.kr/Resource/LabSeminar/Seminar2008-3/XML%20Document%20Parsing-Operational%20and%20Performance%20Characteristics.pdf</p> Another promising XML processing model is vtd-xml http://vtd-xml.sf.net

http://winslab.cnu.ac.kr/Resource/LabSeminar/Seminar2008-3/XML%20Document%20Parsing-Operational%20and%20Performance%20Characteristics.pdf

]]> By: Mihai Danila http://javablog.co.uk/2007/03/29/xml-parsing/comment-page-1/#comment-6808 Mihai Danila Tue, 08 Apr 2008 11:57:01 +0000 http://javablog.co.uk/2007/03/29/xml-parsing/#comment-6808 <p>Because the XML processing libraries, including org.xml.sax.InputSource, can accept streams, they implicitly promise they may be able to handle the conversion of the bytes produced by these streams into characters. And they do---if the "xml" processing instruction contains the "encoding" attribute, then the processor will honor the attribute and use whatever encoding is specified in the XML. This takes some burden away from the program, which need not make assumptions about the encoding, placing some burden on XML authoring, where you might as well specify an encoding.</p> <p>What happens when the "encoding" attribute is missing? It's up to your tool, but I believe that the standard libraries fall back to the platform encoding---ISO-8859-1 on Windows-based operating systems, if I'm not mistaken.</p> Because the XML processing libraries, including org.xml.sax.InputSource, can accept streams, they implicitly promise they may be able to handle the conversion of the bytes produced by these streams into characters. And they do—-if the “xml” processing instruction contains the “encoding” attribute, then the processor will honor the attribute and use whatever encoding is specified in the XML. This takes some burden away from the program, which need not make assumptions about the encoding, placing some burden on XML authoring, where you might as well specify an encoding.

What happens when the “encoding” attribute is missing? It’s up to your tool, but I believe that the standard libraries fall back to the platform encoding—-ISO-8859-1 on Windows-based operating systems, if I’m not mistaken.

]]> By: Sam http://javablog.co.uk/2007/03/29/xml-parsing/comment-page-1/#comment-5 Sam Tue, 10 Apr 2007 09:34:25 +0000 http://javablog.co.uk/2007/03/29/xml-parsing/#comment-5 <p>I wonder if there was a good reason for "UTF-8" not being the default charset, or if this is a legacy issue where someone screwed up. The most annoying thing is that the <code>FileReader</code> class (and its associates) also use the default charset, meaning that although Java is completely UTF-8 safe, the convenience I/O classes aren't.</p> I wonder if there was a good reason for “UTF-8” not being the default charset, or if this is a legacy issue where someone screwed up. The most annoying thing is that the FileReader class (and its associates) also use the default charset, meaning that although Java is completely UTF-8 safe, the convenience I/O classes aren’t.

]]>