[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Invalid tokens

• To: "Jay Blanchard" <jay.blanchard@n...>,<xml-dev@l...>
• Subject: Re: Invalid tokens
• From: "Karl Waclawek" <karl@w...>
• Date: Fri, 12 Nov 2004 10:40:44 -0500
• References: <C8F323573C030A448F3E5A2B6FE2070B03522D7B@nemesis>

Well, ideally this is fixed at the source.
If that is not possible, you can only hope that
the error is always the same, and then come up with
an extra step in processing to correct that error.

I am not aware of any tools that fix mal-formed XML
documents, since in general this is not possible.

Karl

----- Original Message ----- 
From: "Jay Blanchard" <jay.blanchard@n...>
To: "Karl Waclawek" <karl@w...>; <xml-dev@l...>
Sent: Friday, November 12, 2004 10:34 AM
Subject: RE:  Invalid tokens


[snip]
It may very well be that your XML file is actually not well-formed.
In that case, it's the XML file that needs fixing.
[/snip]

Is there a tool, other than brute force, that I can use to fix it? I am
also contacing the creator of the document to make them aware.

To add to the strangeness of this particular problem, when I am parsing
on a system that is using PHP 4.2.1 it gives me no problems (perhaps
checking is a little lax in that version) and I only encountered the
problem when I moved to PHP 4.3.7.

Thx!

• References:
  • RE: Invalid tokens
    • From: "Jay Blanchard" <jay.blanchard@n...>

• Prev by Date: RE: Invalid tokens
• Next by Date: public review of WS-Context v0.8 spec
• Previous by thread: RE: Invalid tokens
• Next by thread: RE: Invalid tokens
• Index(es):
  • Date
  • Thread