Red Hat Bugzilla – Bug 483516
Editor tag presentation
Last modified: 2010-11-23 22:59:25 EST
When the editor tag is used in Author_Group.xml in a branded book, it appears to keep the default publican presentation (attached screenshot).
Created attachment 330575 [details]
There is a good reason the default template for bug reports uses the format it does. It's so developers have useful information when trying to track down bugs. A snippet of DocBook isn't very useful if it works for me and gives me no information I can use to narrow down what the problem could be.
This works fine for me on latest publican and Red Hat brand when compiling the publican Users_Guide with: make BRAND=RedHat html-en-US
You can check the users guide out and test this if you want.
svn co http://svn.fedorahosted.org/svn/publican/trunk/publican/content/docs
Description of problem:
The presentation of the information within the editor tag does not appear consistent with the rest of the Red Hat brand.
Version-Release number of selected component (if applicable):
All four documents I am currently working on look like this when I build them.
Steps to Reproduce:
1. Go to repo I am working in (I will send you the address via email)
2. Build the book
3. View the html version index page.
Information within the editor tag is blue (which is similar to the publican default colours)
I would expect that it should be red (the same colour as as the info in the author tag).
The book had previously been built with the Red Hat brand without any problems. I added the editor tag to author_group and it appears in blue instead of red as I would expect.
It appears that everything in the <editor> tag is a mailto:. I can click anywhere (including "Edited by", orgname & orgdiv) and it will compose a new email.
This issue is related to the empty email tag in the author before the editor. Adding content to the email tag or removing the email tag prevents this issue from occurring.
The easiest way around this is to not include tags you aren't actually using, I'm not sure if it's advisable to handle this pragmatically.