Bug 743792 - Some Book Titles on docs.redhat.com (and docs-stage) are not alpha-sorted.
Summary: Some Book Titles on docs.redhat.com (and docs-stage) are not alpha-sorted.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 2.8
Hardware: i386
OS: Linux
unspecified
low
Target Milestone: 3.0
Assignee: Jeff Fearn 🐞
QA Contact: Ruediger Landmann
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-06 03:14 UTC by Jared MORGAN
Modified: 2015-08-10 01:22 UTC (History)
2 users (show)

Fixed In Version: 3.0.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-31 03:10:54 UTC


Attachments (Terms of Use)

Description Jared MORGAN 2011-10-06 03:14:52 UTC
Description of problem:

If books have upper-case letter strings in the start of the book title, the book is being incorrectly alpha-sorted on the hosting and live docs sites.


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

Publican 2.8


How reproducible:

100%


Steps to Reproduce:
1. Navigate to docs.redhat.com
2. Click JBoss Enterprise Application Platform > 5 in the navigation tree
3. Note the order of book titles.
  
Actual results:

HTTP Connectors Load Balancing Guide appears *before* Hibernate guides.

RESTEasy Reference Guide appears *before* Release Notes


Expected results:

HTTP Connectors Load Balancing Guide appears *after* HornetQ User Guide

RESTEasy Reference Guide appears *after* Release Notes 5.1.1


Additional info:

This also affects docs-stage. It is not just EAP that is affected. Red Hat Enterprise Linux > 6 > DM Multipath is also out of alpha-order.

I spoke to Rudi about this, and he added the following info:

(13:03:45) rudi: Looks like Publican is sorting those titles according to Unicode codepoint

Hope this helps in fixing the issue.

Comment 1 Jeff Fearn 🐞 2011-10-10 10:44:22 UTC
Made string comparison of Product and Book Name case insensitive.

Applied to branch/publican-2x and trunk.

Committed revision 1906.

Comment 2 Jared MORGAN 2012-02-17 01:07:59 UTC
I've checked docs.redhat.com, and this issue no longer presents. I think you're good to close this off, Jeff.


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