[publican-list] [Bug 486520] Preface headings and revision history should use sentence caps

bugzilla at redhat.com bugzilla at redhat.com
Thu Jul 16 04:17:43 UTC 2009


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=486520


David O'Brien <daobrien at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|publican-list at redhat.com    |




--- Comment #6 from David O'Brien <daobrien at redhat.com>  2009-07-16 00:17:42 EDT ---
(In reply to comment #5)
> 0) Identified because I used sentence case for a whole book and Preface and
> Revision History did not.

This would indicate that the balance of the book was at odds with our standing
styles, given that the Preface (in particular) includes sections based on
templates that use initial caps.

> 
> 1) The effect is every book will have the same heading style and be consistent.

You can achieve this effect by adhering to existing styles.

> 
> 2) No time and effort required since even people like myself can remember
> sentence case rules.

The time and effort is required in determining and implementing a new style and
then ensuring that *it*, rather than a previous style, is adhered to.

> 
> 3) For gain see 1).  

It's true that our styles are not consistently applied across all books. That
doesn't mean we need to change. It's also true that there are many styles used
throughout the world. Again, doesn't mean we need to change. Review, sure. If
we identify problems, if there is general agreement, and the benefit is obvious
and outweighs the cost then sure, let's investigate a style change. There are
far too many other aspects of our documentation that need attention besides how
we present our headings.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.




More information about the publican-list mailing list