Lists Home |
Date Index |
1) The tag <xml versionfiltered="1.0" encoding="ISO-8859-1"> activate
a XML parser on a web browser. </xml> will close the parse data.. I
don think the parser will expect more data before the </xml>. But the
web browser is a strange animal, so maybe support multiple <xml>
documents or mixing a xml document with something else. No idea. You
sould not build on undefined beaviors.
2) I dont really know much about SAXParsing. To me Sax sound like a
finland pop group. Maybe theres a Sax solution withing Sax "manual" or
"recipe book". But I guest is a XML parser
3) You are not trying anithing has ben suggested here. Are you?. I
dont expect a error message, If your XHTML file is correct.
4) HTML visualization can be controled with CSS, so that problem is
easy to fix once the browser render the doc.
5) The error message "The element type "meta" must be terminated by
the matching end-tag </meta>" that vulcanian for "He dood, add a
</meta> tag after your data!". A parser can break on a unrelated topic
( ";" and C compilers...) but maybe your doc really lack a </data>
On 7/27/06, Anil Philip <email@example.com> wrote:
> no replies?
> Anil Philip <firstname.lastname@example.org> wrote:
> Dont know if you saw this, but I did put in the xml tags and it does not
> display. However, there is the big problem of the parser choking.
> moving the <?xml versionfiltered="1.0" encoding="ISO-8859-1"?>
> did not fix it.
> However, changing to <xml versionfiltered="1.0" encoding="ISO-8859-1">
> removes the display of xml data on the first line in IE browser.
> But when I try to parse this, I get
> org.xml.sax.SAXParseException: The element type "meta" must be terminated by
> the matching end-tag "</meta>".
> at nodepad.OpenJWO.parseTree(OpenJWO.java:44)
> I have also put the following as the first line in my startElement() and