unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r105834: Capitalize non-function content words in menu item strings.
Date: Mon, 19 Sep 2011 17:19:24 +0300	[thread overview]
Message-ID: <87hb48pqsr.fsf@mail.jurta.org> (raw)
In-Reply-To: <jwvmxe0oeo6.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 19 Sep 2011 09:18:11 -0400")

>> -      `(menu-item ,(purecopy "Show only file buffers")
>> +      `(menu-item ,(purecopy "Show Only File Buffers")
>
> Why do we do that?  I guess one answer can be "because other GUI apps do
> it", but then the question simply becomes: why do they do it?

I presume all apps do it because according to English grammar
function (grammatical) words in titles must be lower case
and content (lexical) words must be capitalized.

The same rule also states that the last function word in a title
must be capitalized.  That means that "to" in the following
menu items currently is grammatically incorrect:

./lisp/arc-mode.el:455:        '(menu-item "Rename to..." archive-rename-entry
./lisp/arc-mode.el:459:      ;;  '(menu-item "Copy to..." archive-copy))
./lisp/dired.el:1780:      '(menu-item "Hardlink to..." dired-do-hardlink
./lisp/dired.el:1783:      '(menu-item "Symlink to..." dired-do-symlink
./lisp/dired.el:1796:      '(menu-item "Rename to..." dired-do-rename
./lisp/dired.el:1799:      '(menu-item "Copy to..." dired-do-copy



  parent reply	other threads:[~2011-09-19 14:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1R5Ojk-0008T4-5r@vcs.savannah.gnu.org>
2011-09-19 13:18 ` [Emacs-diffs] /srv/bzr/emacs/trunk r105834: Capitalize non-function content words in menu item strings Stefan Monnier
2011-09-19 14:03   ` Juanma Barranquero
2011-09-19 14:31     ` Stefan Monnier
2011-09-19 14:19   ` Juri Linkov [this message]
2011-09-19 14:35     ` Juanma Barranquero
2011-09-19 18:43       ` Juri Linkov
2011-09-19 16:07   ` Glenn Morris

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87hb48pqsr.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).