From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: toolbar conventions
Date: Sat, 17 Dec 2005 14:40:49 -0500 [thread overview]
Message-ID: <E1EnhvF-0001vV-Q9@fencepost.gnu.org> (raw)
In-Reply-To: <19466.1134769009@olgas.newt.com> (message from Bill Wohler on Fri, 16 Dec 2005 13:36:49 -0800)
By the way, I checked both the O'Reilly style guide and the Microsoft
style guide and both agreed on "menu bar" and "toolbar." Given that
technical terms go from two words, to a hyphenated form, to a single
word, it's likely that's what we're seeing here.
Menu bars are older than tool bars, so if it were simply a natural
progression, it is peculiar that it has proceeded faster for
tool bars than for menu bars.
Given that, should we be using "toolbar" in both text and code in
anticipation of a future renaming of tool-bar to toolbar?
I tend to think we should treat the two alike. But there is no rush
to change this; let's leave it alone, for now.
Does anyone have any ideas on the issue of how to use the term
"option"? That issue is more important--it is not just an issue of
punctuation, it is inconsistent use of a word. Would someone like to
study the situation and find out which uses occur where?
next prev parent reply other threads:[~2005-12-17 19:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 21:36 toolbar conventions Bill Wohler
2005-12-17 19:40 ` Richard M. Stallman [this message]
2005-12-17 20:22 ` Luc Teirlinck
2005-12-17 20:52 ` Bill Wohler
2005-12-17 22:51 ` Luc Teirlinck
2005-12-18 0:57 ` Drew Adams
2005-12-18 3:11 ` Luc Teirlinck
2005-12-19 19:58 ` Drew Adams
2005-12-19 4:39 ` Richard M. Stallman
2005-12-20 1:52 ` Luc Teirlinck
2005-12-20 3:32 ` Drew Adams
2005-12-20 16:33 ` Richard M. Stallman
2005-12-20 18:37 ` user preferences (was RE: toolbar conventions) Drew Adams
2005-12-22 17:52 ` Richard M. Stallman
2005-12-22 18:09 ` Drew Adams
2005-12-23 15:18 ` Richard M. Stallman
2005-12-22 17:52 ` Richard M. Stallman
2005-12-20 5:12 ` toolbar conventions Glenn Morris
2005-12-17 20:26 ` Bill Wohler
2005-12-18 17:15 ` Richard M. Stallman
2005-12-18 20:45 ` Bill Wohler
2005-12-19 23:46 ` Richard M. Stallman
2005-12-17 20:30 ` Luc Teirlinck
2005-12-18 18:41 ` Luc Teirlinck
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=E1EnhvF-0001vV-Q9@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
/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).