Bug 873586 - "Draft" watermark does not display in PDF
Summary: "Draft" watermark does not display in PDF
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 3.1
Assignee: Jeff Fearn 🐞
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-06 09:10 UTC by Anjana Suparna Sriram
Modified: 2013-02-06 03:40 UTC (History)
4 users (show)

Fixed In Version: 3.1.0
Clone Of:
Environment:
Last Closed: 2013-02-06 03:40:49 UTC
Embargoed:


Attachments (Terms of Use)

Description Anjana Suparna Sriram 2012-11-06 09:10:07 UTC
Description of problem: The draft watermark is not shown when the book is rendered in PDF but it is shown in HTML output.


Version-Release number of selected component (if applicable): publican-3.0-0.fc17.t216.noarch


How reproducible: Always


Steps to Reproduce:
1. Include book status as draft in book_name.xml and show remarks=1 in publican.cfg 
2. Run publican build command
3. PDF does now show the draft watermark.
  
Actual results:
PDF does now display the draft watermark

Expected results:

All outputs show the watermark.

Additional info:

Comment 1 Jeff Fearn 🐞 2013-01-11 06:07:49 UTC
This fix has been committed to the devel branch for inclusion in Publican 3.1.

Fix actually required updating the XSL as wkhtmltopdf will not display the background of the body tag.

Comment 2 xuezhi ma 2013-01-29 02:55:44 UTC
Verify version: publican-3.1.0-0.el6eng.noarch  - PASS

Verify steps:
1. Create a document with $publican create --name=test
2. vim en-US/test.xml, edit <book status="draft"> and set show_remarks:1 in publican.cfg
3. Build the book in PDF format, then check the watermark.

Actual results:
"Draft" watermark is displayed in PDF document.

Additional info:
There is no "Draft" watermark in table of contents page of PDF document, see bug 905271


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