From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: Why are and not called and ? Date: Sat, 2 Sep 2006 06:46:52 -0700 Message-ID: References: <44F93862.9070004@student.lu.se> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1157204840 10857 80.91.229.2 (2 Sep 2006 13:47:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 2 Sep 2006 13:47:20 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Sep 02 15:47:18 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GJVqA-0003U6-8p for ged-emacs-devel@m.gmane.org; Sat, 02 Sep 2006 15:47:18 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GJVq9-0004GA-T3 for ged-emacs-devel@m.gmane.org; Sat, 02 Sep 2006 09:47:17 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GJVpv-0004BS-Oe for emacs-devel@gnu.org; Sat, 02 Sep 2006 09:47:04 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GJVpt-00045p-5X for emacs-devel@gnu.org; Sat, 02 Sep 2006 09:47:02 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GJVpt-00045a-1Z for emacs-devel@gnu.org; Sat, 02 Sep 2006 09:47:01 -0400 Original-Received: from [141.146.126.228] (helo=agminet01.oracle.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.52) id 1GJVzx-0007T0-SB for emacs-devel@gnu.org; Sat, 02 Sep 2006 09:57:26 -0400 Original-Received: from rgmsgw02.us.oracle.com (rgmsgw02.us.oracle.com [138.1.186.52]) by agminet01.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k82DkxEn009053 for ; Sat, 2 Sep 2006 08:46:59 -0500 Original-Received: from dradamslap (dhcp-amer-whq-csvpn-gw3-141-144-80-55.vpn.oracle.com [141.144.80.55]) by rgmsgw02.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id k82DkwS0016060 for ; Sat, 2 Sep 2006 07:46:58 -0600 Original-To: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-reply-to: <44F93862.9070004@student.lu.se> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:59255 Archived-At: >> May I then suggest a little smaller change for this instead? Could we >> have a human readable table with translations from internal key names >> like , to standard keyboard names? Just those names that >> differ should go into the table of course. >> >> That's a good suggestion. It should be phrased in terms of "often >> used as labels on many keyboards" etc., to avoid giving the >> impression that this is standard; it is common among many keyboards, >> but it is by no means standard (there is no standard for such labels >> AFAIK). >> > > Maybe the "Emacs terminology" info page is a reasonable place for > that? It is not really Emacs terminology, but people might look for > it there. That is fine for me. (And I think it is about Emacs terminology.) It is about terminology, but it not much about Emacs terminology. Any other app that let you talk about keys (e.g. bind them) would have the same terminological difficulty, because there is a canonical (X11) name for the key that is different from what is printed on the key itself. Node "Keys" or somewhere under node "Key Bindings" is where I think someone would try to look up what these keys are about and what they're called. `i key' takes you to node "Keys", for instance. Perhaps mention this in both places (Emacs Terminology and Keys or somewhere under Key Bindings), by using a cross reference? Also, we might add index entries for Page Up, Page Down, next, and prior (though `next' will probably get lots of hits), so someone can get to the explanation directly.