RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 967359 - duplicated indexes in summary
Summary: duplicated indexes in summary
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-High_Availability_Add-On_Overview
Version: 6.1
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-26 20:02 UTC by manuel wolfshant
Modified: 2015-02-20 16:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-20 16:25:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
highlight of the overlapping indexes (80.77 KB, image/jpeg)
2013-05-26 20:02 UTC, manuel wolfshant
no flags Details

Description manuel wolfshant 2013-05-26 20:02:37 UTC
Created attachment 753374 [details]
highlight of the overlapping indexes

Document URL: 
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/High_Availability_Add-On_Overview/

Section Number and Name: 
Introduction


Describe the issue: 

The first 2 parts of the introduction (1 Document conventions and 2. We Need Feedback!) have indexes which overlap with those of the first 2 chapters and make navigation via the summary links incorrect
See the attached snapshot

Suggestions for improvement: 
 Define correct indexes


Additional information:

Comment 2 Steven J. Levine 2014-07-17 19:49:36 UTC
The appearance of the numbering within prefaces/introductions is how the books build, and this is how it appears in all of the documents on the Customer portal, numbered like this: The main sections of the prefaces are numbers as 1, 2, etc.  And the main chapters are numbered as 1, 2.

I will look into finding out where to address this BZ, but it's not specific to this document.

Comment 3 manuel wolfshant 2014-07-17 23:09:20 UTC
What can I say? 25 years ago when I started to use multilevel lists, having the summary not functional because of incorrect indexes was considered an error and led to the proof reader rejecting that particular version of the document. But of course one can always go with a "good enough" policy.

Comment 4 Steven J. Levine 2014-07-18 14:33:21 UTC
I can't say that I like it myself.

Comment 5 Steven J. Levine 2014-07-28 16:08:24 UTC
With 6.6 Beta about to go out the door, for administrative reasons I'm moving this to 6.7 until I can determine where to pass this information along. It may be an RFE for publican itself -- that's my current thought -- which is not connected to any particular release.

Comment 6 Steven J. Levine 2015-02-20 16:25:08 UTC
I am no longer seeing this issue in the latest builds on the Portal (there has been some work on re-doing the formatting through Publican, including streamlining what appears) so I'm closing this Bug.


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