unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, 3516@debbugs.gnu.org
Subject: bug#3516: 23.0.94; function key names in Info
Date: Tue, 12 Jul 2011 20:15:27 +0300	[thread overview]
Message-ID: <8362n7fmj4.fsf@gnu.org> (raw)
In-Reply-To: <E4EC0BEE2B2E441187A216F08002ACF3@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <3516@debbugs.gnu.org>
> Date: Tue, 12 Jul 2011 09:38:24 -0700
> 
> > "@key{F1}" in Texinfo produces "<F1>" in Info,
> > without the single quotes.  In the printed output it produces
> > something resembling a keyboard key with a label on it.  Taking these
> > in quotes would be wrong, e.g. because then "@kbd{C-x @key{RET}}"
> > would produce `C-x `<RET>'' with nested quotes which looks ugly.
> 
> What you describe is an implementation problem (Texinfo, Info).

Actually, no: _you_ are talking about implementation.

There are no quotes in the manual sources here, there are 2 different
markups: @kbd and @key.  They are different because they express two
different entities: characters typed by the user on the keyboard as
opposed to a single special key named by its label.  The quotes in one
of the cases are the Info way of _implementing_ the @kbd markup.  Note
that the printed manual doesn't have these quotes, because there @kbd
produces slanted typeface that stands out without any need to quote
it.  Likewise with the other formats supported by the Texinfo package.
Only the Info and the plain text formats use quotes -- it's their
_implementation_ of the @kbd markup.

> What I describe is from a user point of view: the resulting appearance in the
> Info manual.

There's nothing wrong with the appearance.

> The point is that `<RET>' should be used.

According to you.  According to 25-year long practice of writing GNU
manuals, practice that is codified in the Texinfo manual (which is a
de-facto standard for writing GNU documentation), @key{RET} should be
used, and in Info it produces <RET> without quotes.

If you want to request a change in the _implementation_ of @key in the
Info format, the place to request that is in the Texinfo mailing list,
not here.

> The entire key sequence - whatever that key sequence is, should be in quotes,
> consistently, to indicate a key sequence.  `C-x <RET>' and `<RET>' both
> correspond to the same convention: put the sequence of keys in quotes.

<RET> is not a key sequence, it's a single key named by its label.

Again, the distinction between @kbd and @key is very basic.  If you
disagree with it, at least accept that this is widely used practice in
GNU documentation and is explicitly described in the Texinfo manual.

IOW, this is how the GNU project documents its software, whether you
like it or not.  And no amount of bugs filed against Emacs will be
able to change that.





  reply	other threads:[~2011-07-12 17:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 16:11 bug#3516: 23.0.94; function key names in Info Drew Adams
2009-06-10 22:23 ` Eli Zaretskii
2009-06-10 22:33   ` Drew Adams
2009-06-11 10:42     ` Eli Zaretskii
2009-06-11 15:33       ` Drew Adams
2011-07-12 12:47 ` Lars Magne Ingebrigtsen
2011-07-12 16:00   ` Eli Zaretskii
2011-07-12 16:38     ` Drew Adams
2011-07-12 17:15       ` Eli Zaretskii [this message]
2011-07-12 20:04         ` Drew Adams
2011-07-12 20:30           ` Eli Zaretskii
2011-07-12 21:03             ` Drew Adams
2011-07-13  3:00               ` 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

  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=8362n7fmj4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=3516@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.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).