Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bob Wilson <bwilson@tensilica.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] consistently capitalize section names
Date: Mon, 26 Mar 2007 20:50:00 -0000	[thread overview]
Message-ID: <ufy7rafw8.fsf@gnu.org> (raw)
In-Reply-To: <46081016.3030204@tensilica.com> (message from Bob Wilson on Mon, 	26 Mar 2007 11:25:26 -0700)

> Date: Mon, 26 Mar 2007 11:25:26 -0700
> From: Bob Wilson <bwilson@tensilica.com>
> 
> With the exception of some of the more recently written parts of the GDB doc, 
> there appears to be a strong convention of capitalizing only the first word of 
> section titles.  (All the major words in chapter and appendix titles are 
> capitalized.)  Some of the section titles do not follow this convention.  This 
> is most visible when you read the table of contents in the TeX-generated output. 
>   This patch makes all the section titles consistently capitalized.

Thanks for doing this, but unfortunately the capitalization style
you've chosen is wrong.  The Texinfo manual says:

   * By convention, node names are capitalized just as they would be for
     section or chapter titles--initial and significant words are
     capitalized; others are not.

IOW, the correct capitalization style is, e.g., "Commands to Set
Tracepoints", not "Commands to set tracepoints".  If you can afford
that, please redo the capitalization to use this style.

Thanks again for working on this.


  reply	other threads:[~2007-03-26 20:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 18:25 Bob Wilson
2007-03-26 20:50 ` Eli Zaretskii [this message]
2007-03-26 21:20   ` Bob Wilson
2007-03-27  4:06     ` Eli Zaretskii
2007-03-27 19:35       ` Bob Wilson
2007-03-31 11:48         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ufy7rafw8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bwilson@tensilica.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox