Bug 846812 - Parsing errors generated on Revision_History.xml now do not specify the XML file/error
Summary: Parsing errors generated on Revision_History.xml now do not specify the XML f...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 3.0
Assignee: Jeff Fearn 🐞
QA Contact: Ruediger Landmann
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-08 19:21 UTC by Stephen Gordon
Modified: 2012-10-31 03:11 UTC (History)
2 users (show)

Fixed In Version: 3.0.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-31 03:11:32 UTC
Embargoed:


Attachments (Terms of Use)

Description Stephen Gordon 2012-08-08 19:21:20 UTC
Description of problem:

When publican encounters a parsing error in the Revision_History.xml file, which is now parsed before the rest of the XML, the error doesn't specify what or where the problem is.

Mismatched firstname and/or surname tags caused the error in my case, but the only reason I realised this was because the only file I had changed was Revision_History.xml and it failed an xmllint when I ran it directly.

Version-Release number of selected component (if applicable):

publican-3.0-0.fc17.t216.noarch

Additional Information:

$ rhpkg publican build --langs=en-US --formats=html

mismatched tag at line 17, column 6, byte 565 at /usr/lib64/perl5/vendor_perl/XML/Parser.pm line 187

Comment 1 Ruediger Landmann 2012-08-15 06:33:23 UTC
Fix verified in build publican-3.0-0.fc17.t219.noarch:

Beginning work on en-US
DTD Validation failed: 
Revision_History.xml:8: validity error : Element revision is not declared in simpara list of possible children
Revision_History.xml:9: validity error : Element revision content does not follow the DTD, expecting (revnumber? , date , (author | authorinitials)* , (revremark | revdescription)?), got ()


Note You need to log in before you can comment on or make changes to this bug.