Bug 905271 - "Draft" watermark does not display in Table of Contents page in PDF
Summary: "Draft" watermark does not display in Table of Contents page in PDF
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 3.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: 3.2
Assignee: Jeff Fearn 🐞
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-29 02:45 UTC by xuezhi ma
Modified: 2014-11-18 02:20 UTC (History)
5 users (show)

Fixed In Version: 3.2.0
Clone Of:
Environment:
Last Closed: 2013-08-09 04:48:35 UTC
Embargoed:


Attachments (Terms of Use)

Description xuezhi ma 2013-01-29 02:45:53 UTC
Description of problem:
In PDF documents, there is no "draft" watermark in table of contents page, and only part of "draft" can be seen in some pages.

Version-Release number of selected component (if applicable):
publican-3.1.0-0.el6eng.noarch

How reproducible:
always

Steps to Reproduce:
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:
1. "Draft" watermark does not display in Table of Contents page in PDF document.
2. Only part of "draft" can be seen in some pages.

Expected results:
1. "Draft" watermark should be displayed in Table of Contents page in PDF document.
2. The whole part of "draft" can be shown in all pages, and hope they have the same position in each pages.

Additional info:

Comment 1 HSS Product Manager 2013-07-16 05:18:01 UTC
HSS-QE has reviewed and declined this request. QE for this bug will be handled by IED.

Comment 2 Jeff Fearn 🐞 2013-07-17 06:21:47 UTC
To ssh://git.fedorahosted.org/git/publican.git
   e8ee65f..ecb6f83  HEAD -> devel

Comment 3 Scott Radvan 2013-07-19 03:01:13 UTC
verified with publican-3.1.5-0.fc19.t61.noarch

Comment 4 Jeff Fearn 🐞 2013-08-09 04:48:35 UTC
The fix for this bug has been shipped in publican 3.2.0


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