[publican-list] [Bug 461222] New: template creates an Author_Group.xml file using a banned tag

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: template creates an Author_Group.xml file using a banned tag

https://bugzilla.redhat.com/show_bug.cgi?id=461222

           Summary: template creates an Author_Group.xml file using a
                    banned tag
           Product: Red Hat Enterprise Linux 5
           Version: 5.2
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: medium
         Component: publican
        AssignedTo: jfearn at redhat.com
        ReportedBy: lbrindle at redhat.com
         QAContact: mhideo at redhat.com
                CC: publican-list at redhat.com
   Estimated Hours: 0.0
    Classification: Red Hat


Description of problem:
When creating a book with create_book, the generated Author_Group.xml file
contains a <corpauthor> tag, which will break a build.

Version-Release number of selected component (if applicable):
publican-0.36-6.el5

How reproducible:
Every time

Steps to Reproduce:
1. Run create_book
2. Navigate to the Author_Group.xml file
3. See banned tags

Actual results:
<authorgroup>
 <corpauthor>FF0000 Headgear Documentation Group</corpauthor>
 <author>
  <firstname>Dude</firstname>
  <surname>McDude</surname>
  <affiliation>
   <orgname>My Org</orgname>
   <orgdiv>Best Div in the place</orgdiv>
  </affiliation>
  <email>dude.mcdude at myorg.org</email>
 </author>
</authorgroup>


Expected results:
<authorgroup>
 <author>
  <firstname>Dude</firstname>
  <surname>McDude</surname>
  <affiliation>
   <orgname>My Org</orgname>
   <orgdiv>Best Div in the place</orgdiv>
  </affiliation>
  <email>dude.mcdude at myorg.org</email>
 </author>
</authorgroup>


Additional info:

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.