Bug 1386101

Summary: [RHEL 6][Doc bug]Errors in PDF copies of product documentation
Product: Red Hat Enterprise Linux 6 Reporter: Sandeep <snikam>
Component: doc-Performance_Tuning_GuideAssignee: Milan Navratil <mnavrati>
Status: CLOSED DUPLICATE QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.9CC: rhel-docs, tcapek
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-29 16:52:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Screen shot of the iusues customer has pointed. none

Description Sandeep 2016-10-18 07:10:09 UTC 
Created attachment 1211619 [details]
Screen shot of the iusues customer has pointed.

The PDF document for RHEL 6 Performance Tuning (https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/pdf/Performance_Tuning_Guide/Red_Hat_Enterprise_Linux-6-Performance_Tuning_Guide-en-US.pdf) on pages 68-69 has the text split such that the top halves of letters on the last line print on page 68 while the bottom halves of letters print as the top line on page 69.

A similar issue is seen in the Table of Contents in the same document on pages 1, 2, and 3. Some of the grey terminal or source code boxes also show a similar "margin cut-off" appearance, although it seems the text has survived unscathed in these examples: pages 41-42, and 62-63, 

The RHEL 6.8 Technical Notes and Release Notes and RHEL 7.2 Release Notes show the same problems in their Tables of Contents, as does the RHEL 7 Atomic Host 7 Getting Started with Containers document. Looks likely that any document which has the Table of Contents split across multiple pages could exhibit this problem.
Comment 4 Jaromir Hradilek 2016-11-29 16:52:39 UTC 
Hi Sandeep,

Thank you very much for taking the time to report this issue. Unfortunately, this issue is not unique to the Performance Tuning Guide and since the problem is in the tool that produces the PDF output, there's nothing the documentation team can do to fix it. This is, however, a known issue and the tooling team is already aware of it.

I am closing this bug as a duplicate of bug 1144616.

Thank you,
Jaromir

*** This bug has been marked as a duplicate of bug 1144616 ***