From noreply at sourceforge.net Fri Mar 16 10:00:19 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 16 Mar 2007 02:00:19 -0700 Subject: [Expat-bugs] [ expat-Bugs-1681926 ] Parse error on well formed XML file Message-ID: Bugs item #1681926, was opened at 2007-03-16 02:00 Message generated for change (Tracker Item Submitted) made by Item Submitter 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: Open Resolution: None 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1681926&group_id=10127 From noreply at sourceforge.net Fri Mar 16 15:31:30 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 16 Mar 2007 07:31:30 -0700 Subject: [Expat-bugs] [ expat-Bugs-1681926 ] Parse error on well formed XML file Message-ID: 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: Open Resolution: None 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-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 From 034710 at gmail.com Tue Mar 20 18:54:18 2007 From: 034710 at gmail.com (Stephen Cartwright) Date: Tue, 20 Mar 2007 11:54:18 -0600 Subject: [Expat-bugs] Make check fails expat 2.0.0 In-Reply-To: <6e5bf8160703201051kda3b02bhc19d2c4a6a76c329@mail.gmail.com> References: <6e5bf8160703201051kda3b02bhc19d2c4a6a76c329@mail.gmail.com> Message-ID: <6e5bf8160703201054s781fcb3bt857dc7eac1191a1@mail.gmail.com> Actually it looks like the problem is make check is calling g++ ... Do you think expat works properly though? On 3/20/07, Stephen Cartwright <034710 at gmail.com> wrote: > Hi, > > I am trying to get expat to work on a Tru64 5.1B machine I have at work. > > configure and make are OK, but make check fails (see attached). > > Thanks in advance for any assistance. > > Steve > > -- Stephen Cartwright - sgcartwr at ucalgary.ca HPC/Research Support - Information Technologies University of Calgary - Calgary, Alberta, Canada Phone: (403) 220-2101 | Fax: (403) 282-9199 From 034710 at gmail.com Tue Mar 20 18:51:40 2007 From: 034710 at gmail.com (Stephen Cartwright) Date: Tue, 20 Mar 2007 11:51:40 -0600 Subject: [Expat-bugs] Make check fails expat 2.0.0 Message-ID: <6e5bf8160703201051kda3b02bhc19d2c4a6a76c329@mail.gmail.com> Hi, I am trying to get expat to work on a Tru64 5.1B machine I have at work. configure and make are OK, but make check fails (see attached). Thanks in advance for any assistance. Steve -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: expat_install.txt Url: http://mail.libexpat.org/pipermail/expat-bugs/attachments/20070320/b075be2c/attachment-0001.txt From noreply at sourceforge.net Thu Mar 29 22:31:42 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 29 Mar 2007 13:31:42 -0700 Subject: [Expat-bugs] [ expat-Bugs-1690883 ] Expat rejects xml: prefix with "unbound prefix" error. Message-ID: Bugs item #1690883, was opened at 2007-03-29 15:31 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1690883&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: Open Resolution: None Priority: 5 Private: No Submitted By: Scott Klement (klemscot) Assigned to: Nobody/Anonymous (nobody) Summary: Expat rejects xml: prefix with "unbound prefix" error. Initial Comment: When namespace handling is enabled, Expat considers the following document invalid: Foo The error is "Unbound prefix", referring to the "xml:" prefix. However, according the W3C spec, it's not necessary to declare that particular prefix. I'm looking at the following document: http://www.w3.org/TR/REC-xml-names/ Under chapter 3, subheading "Namespace constraint: Reserved Prefixes and Namespace Names" This is the section I'm reading: The prefix xml is by definition bound to the namespace name http://www.w3.org/XML/1998/namespace. ****It MAY, but need not, be declared****, and MUST NOT be bound to any other namespace name. Other prefixes MUST NOT be bound to this namespace name, and it MUST NOT be declared as the default namespace. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1690883&group_id=10127