Bug 592822

Summary: JBoss brand PDF <term> style differs from HTML
Product: [Community] Publican Reporter: Laura Bailey <lbailey>
Component: publicanAssignee: Ruediger Landmann <rlandman+disabled>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 1.6CC: jfearn, mmcallis, publican-list, rlandman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: 2.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-05 00:15:01 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Laura Bailey 2010-05-17 01:12:44 EDT
Description of problem:
When using the publican-jboss brand to output HTML and PDF documents, the styling of the <term/> text in a <variablelist/> differs. In HTML, the output is always strong red text; in PDF, it is normal text unless affected by other markup.

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

How reproducible:
Every time, regardless of other markup (<classname>, <varname>, etc.) or lack thereof. HTML outputs strong red text for terms; PDF varies between the strong/normal text depending on the additional markup.

Steps to Reproduce:
1. Build book with variablelist, for example:
2. Check HTML and PDF output for variablelist styling
Actual results:
HTML and PDF variablelists differ in style.

Expected results:
HTML and PDF variablelists should have similar styling - red text for terms, black text for descriptions.

Additional info:

Let me know if you need anything else!
Comment 1 Jeff Fearn 2010-06-10 00:50:49 EDT
Removed color setting for term from default brand and all brands that overrode it. Tested in on command lists in PUG, bold black looks much better to me.

When we push the next version of Publican we will need to rebuild the following brands as well:


Fixed in Build: 1.6.3-0.t102