all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Xue Fuqiao'" <xfq.free@gmail.com>,
	"'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: RE: [Emacs-diffs] /srv/bzr/emacs/trunk r111816: * lisp/menu-bar.el(menu-bar-tools-menu): Fix case of EDE entry.
Date: Sun, 17 Feb 2013 11:20:45 -0800	[thread overview]
Message-ID: <19194CE5D764449083CCF6814B538D8C@us.oracle.com> (raw)
In-Reply-To: <20130217232707.b03e9a514cf5b249b5060b8c@gmail.com>

> > > -      '(menu-item "Project support (EDE)"
> > > +      '(menu-item "Project Support (EDE)"
> > FWIW, I prefer the "less capitalized" forms.
> 
> Maybe it can be written into the "Tips and Conventions" 
> section in elisp manual (if most people approve of it).

1. The most important things are (a) to be fairly consistent across a given
context (e.g. a mode or an application) and (b) to use the same capitalization
as found in the application, for any terms that serve more or less like proper
nouns there (e.g. the name of a buffer that serves as a menu item in menu
`Buffers', or an Imenu menu item).

2. Emacs Dev can decide what it wants, beyond that.  The two most common
capitalization conventions are (a) title case and (b) sentence case (sometimes
called downstyle).  Title case generally means capitalizing the important words
(plus the first), not all the words (sometimes called start case).

3. Historically, title case has tended to be used more in the US; sentence case
in Europe and the UK.  Dunno about other areas, and usage no doubt varies across
media and contexts.

4. #1b means that, barring some other typographical notation to set off such
proper terms, sentence case is advantageous when the proper term is itself
capitalized, and title case is advantageous when it is not.  IOW, what is odd
stands out.

5. "The less capitalized forms" is not very operational as guidance.  Presumably
what Stefan expresses is a preference for sentence case in menus, as opposed to
title case or to capitalizing every word.

6. Personally, I favor title case in menus (but again see #1: be consistent).  I
do so in part because it is overwhelmingly used in menus (to my knowledge), both
within Emacs and beyond, and in part because it leads your eye to terms that
more important, facilitating scanning.

7. Emacs generally sets off menu names using `...' in the manual (e.g., "Click
on `Set Default Font' in the `Options' menu", "click on the menu item named
`Source Code Parsers (Semantic)' in the `Tools' menu").

But sometimes it does not (bugs), and in those cases another advantage to title
case is that it can be easier to separate visually from the surrounding text.

8. I agree that whatever convention is decided on, it would be good to mention
it in the manual, as a guideline.  That helps people know what is generally
preferred.

Given the fact that Emacs already appears pretty consistent in this regard, I
thought that title case had already been chosen as our convention, but whatever
the choice is, it would be good to document it, as guidance.

http://en.wikipedia.org/wiki/Letter_case




  reply	other threads:[~2013-02-17 19:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1U6vh0-0002fR-HZ@vcs.savannah.gnu.org>
2013-02-17 15:05 ` [Emacs-diffs] /srv/bzr/emacs/trunk r111816: * lisp/menu-bar.el (menu-bar-tools-menu): Fix case of EDE entry Stefan Monnier
2013-02-17 15:27   ` Xue Fuqiao
2013-02-17 19:20     ` Drew Adams [this message]
2013-02-17 23:59       ` [Emacs-diffs] /srv/bzr/emacs/trunk r111816: * lisp/menu-bar.el(menu-bar-tools-menu): " Xue Fuqiao
2013-02-18  0:39         ` Drew Adams
2013-02-20 22:24           ` Xue Fuqiao
2013-02-20 23:04             ` Drew Adams
2013-02-17 19:09   ` [Emacs-diffs] /srv/bzr/emacs/trunk r111816: * lisp/menu-bar.el (menu-bar-tools-menu): " Glenn Morris
2013-02-17 19:22     ` [Emacs-diffs] /srv/bzr/emacs/trunk r111816: * lisp/menu-bar.el(menu-bar-tools-menu): " Drew Adams
2013-02-18  0:06     ` [Emacs-diffs] r111816: * lisp/menu-bar.el (menu-bar-tools-menu): " Stephen Berman

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=19194CE5D764449083CCF6814B538D8C@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=xfq.free@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.