Bug 915423 - DocBook 5 <info> and <biblioid> tags should not generate WARNING
Summary: DocBook 5 <info> and <biblioid> tags should not generate WARNING
Keywords:
Status: CLOSED DUPLICATE of bug 915428
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-25 17:32 UTC by Fintan Bolton
Modified: 2016-08-16 01:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-17 11:11:30 UTC
Embargoed:


Attachments (Terms of Use)
Sample Book_Info.xml file updated to DocBook 5 (1.36 KB, text/xml)
2013-02-25 17:32 UTC, Fintan Bolton
no flags Details

Description Fintan Bolton 2013-02-25 17:32:50 UTC
Created attachment 702450 [details]
Sample Book_Info.xml file updated to DocBook 5

Description of problem:

Publican emits a WARNING for the tags 'info' and 'biblioid'. These tags are required by DocBook 5 however: the 'info' tag supersedes the DB4 'bookinfo' tag and the 'biblioid' tag supersedes the DB4 'pubsnumber' tag.  These tags ought to be added to the list of allowed tags, because they are needed for DocBook 5.


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


How reproducible:

Build any DocBook 5 book using the common-db5 base brand and the attached sample Book_Info.xml file.


Steps to Reproduce:
1.
2.
3.
  
Actual results:

*WARNING: Unvalidated tag: 'info'. This tag may not be displayed correctly, may generate invalid xhtml, or may breach Section 508 Accessibility standards.
...
*WARNING: Unvalidated tag: 'biblioid'. This tag may not be displayed correctly, may generate invalid xhtml, or may breach Section 508 Accessibility standards.



Expected results: No warnings.


Additional info:

Comment 1 Jeff Fearn 🐞 2013-07-17 11:11:30 UTC

*** This bug has been marked as a duplicate of bug 915428 ***


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