[Expat-bugs] [ expat-Bugs-1681926 ] Parse error on well formed XML file

SourceForge.net noreply at sourceforge.net
Sat Apr 28 17:35:14 CEST 2007


Bugs item #1681926, was opened at 2007-03-16 05:00
Message generated for change (Comment added) made by kwaclaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1681926&group_id=10127

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Parse error on well formed XML file

Initial Comment:
When a XML file's EOF comes with the last token's end of line, Expat reports a parse error

Error Reported 
not well-formed (invalid token)

Expat Version : 2.0.0

This issue goes off if a new line is given after the last token.


----------------------------------------------------------------------

>Comment By: Karl Waclawek (kwaclaw)
Date: 2007-04-28 11:35

Message:
Logged In: YES 
user_id=290026
Originator: NO

I checked the attached file, it parses OK here. It contains only
whitespace (#xA) after the last element tag. That is allowed, as the spec
allows comments, processing instructions and whitespace (#x20 | #x9 | #xD |
#xA) at the end.

Closing this issue - not a bug.

----------------------------------------------------------------------

Comment By: Karl Waclawek (kwaclaw)
Date: 2007-03-16 10:31

Message:
Logged In: YES 
user_id=290026
Originator: NO

Do you mean an actual EOF character? If I remember correctly, this would
be an illegal character for an XML document, so Expat would have to reject
it.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1681926&group_id=10127


More information about the Expat-bugs mailing list