Re: XML parsing: no EndElement for combined start/end tags

Tech-Archive recommends: Fix windows errors by optimizing your registry

Zytan,

You are going to have to provide a piece of code to show what you are
saying. Personally, I don't see it as an issue, as the infoset has no
concept of what an end tag is. That's something that is up to how you
represent the infoset (and the infoset does not have to be represented as a
text file, as WCF proves).

If you could provide the files that you are reading, and the code you
are using to read them, it would help greatly.


--
- Nicholas Paldino [.NET/C# MVP]
- mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx

"Zytan" <zytanlithium@xxxxxxxxx> wrote in message
news:1175630032.937309.79130@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Have you checked the files themselves in say, notepad?

Yes. This is how I confirmed that what I mention in the above post is
happening. Those are the results of what notepage shows, the actual
text file itself.

IE applys a
transformation on any XML that doesn't already have one applied to it to
produce the interactive HTML view that you see (with the collapsing
elements, etc, etc).

Yes, and this is where I noticed that IE decides that the two-line
case is identical to the one-line case, which the XML standard
indicates is true, also. Thus, an XML parser should correctly show
that BOTH start tag and end tag exists, regardless of the underlying
text-coding.

Your XML files should be coming out correctly. If not, can you show
the
code that you are using to generate them?

I am not creating the XML files, but I have shown the code above as a
small example to show to exactly what the XML files are like. The
problem is not in the creation, and wondering why IE makes them look
different. IE 'standardizes' them in that it shows what the file
logically stands for, regardless of the underlying text-code, to make
it easy to read (good job, IE). The problem is that why does IE parse
them correctly, according to the standard, but the .NET framework does
not? So much is based on XML files that I am astounded that this
issue has not been raised. I have start tag + end tags in one line of
text code, and .NET is telling me no end tag (EndElement) exists!

Zytan




.

Relevant Pages