all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: emacs-devel@gnu.org
Subject: Re: Divergence in menu appearance between Emacs Info and standalone Info
Date: Thu, 5 Jun 2003 12:27:50 +0000 (UTC)	[thread overview]
Message-ID: <m19NtqQ-000IetC@rattlesnake.com> (raw)
In-Reply-To: <200306041404.h54E4SO30552@f7.net> (karl@freefriends.org)

   I gather the default is to hide the node names.  

Yes.  This is and has been a mistake.  It harms GNU documentation.

Texinfo uses node names to structure an Info file, and section headers
to structure a typeset file.  Although the two may be the same, they
should be different in every GNU manual.

The Texinfo manual talks about this in a node called:

    (texinfo)Menu Location

which does *not* have a section title.  While the text of the node
appears in a printed manual, the title does not.  The text appears as
part of the first section of the chapter on Menus.

There is good reason for this:

      By convention, a menu is put at the end of a node since a reader
    who uses the menu may not see text that follows it.  Furthermore,
    a node that has a menu should not contain much text. If you have a
    lot of text and a menu, move most of the text into a new
    subnode--all but a few lines.  Otherwise, a reader with a terminal
    that displays only a few lines may miss the menu and its
    associated text.  As a practical matter, you should locate a menu
    within 20 lines of the beginning of the node.

      The short text before a menu may look awkward in a printed
    manual.  To avoid this, you can write a menu near the beginning of
    its node and follow the menu by an `@node' line, and then an
    `@heading' line located within `@ifinfo' and `@end ifinfo'.  This
    way, the menu, `@node' line, and title appear only in the Info
    file, not the printed document.


It does not matter to readers so much that the printed manual looks
different from the online manual; after all, people expect a printed
manual to be more limited in many ways -- for example, you cannot
conveniently navigate through a printed manual using regular
expression searches.  

(You cannot conveniently navigate through a multi-page HTML site
either, which is why Web sites are still more backward than Info.
Hiding node names in Info may lead some people to think falsely that
Texinfo is as bad as HTML.)

The surface expression of Info should reflect its deep representation
more closely than a printed surface expression.  Quite simply, it is
dangerous to provide a online manual that does not tell users
implicitly that node names are more important than section titles.

Rather than hide node names, it would make more sense to modify Info
to hide section titles than the reverse.

Note that the first part of a menu entry is the menu entry name; that
first part is *not* the section title.  (I sometimes get the
impression that poor writers think a menu entry is the name of a
section.)

A menu does not contain a obligatory section title slot.  The `C-c C-c
C-d' (`texinfo-start-menu-description') Texinfo mode command inserts a
node's section or chapter title in the space for the description in a
menu entry line in the far right hand part of the line -- in the
`description' slot, not in the entry name or node name slots.  This
makes it easy to modify the section title text to provide a better
description.

Since we want good GNU documentation, and since node names are such an
important part of good Texinfo writing, we should keep node names
visible in Info.  It is and has been a mistake to hide the node names
in Info.

-- 
    Robert J. Chassell                         Rattlesnake Enterprises
    http://www.rattlesnake.com                  GnuPG Key ID: 004B4AC8
    http://www.teak.cc                             bob@rattlesnake.com

  parent reply	other threads:[~2003-06-05 12:27 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04 14:04 Divergence in menu appearance between Emacs Info and standalone Info Karl Berry
2003-06-04 14:26 ` Miles Bader
2003-06-04 15:01 ` Stefan Monnier
2003-06-04 15:24   ` Eli Zaretskii
2003-06-04 15:31     ` Stefan Monnier
2003-06-04 16:55       ` Luc Teirlinck
2003-06-04 17:14         ` Stefan Monnier
2003-06-05  2:38           ` Luc Teirlinck
2003-06-05  3:23             ` Miles Bader
2003-06-05  5:52           ` Eli Zaretskii
2003-06-05 13:35             ` Stefan Monnier
2003-06-06  9:46               ` Eli Zaretskii
2003-06-06 11:28                 ` Andreas Schwab
2003-06-06 15:38                 ` Stefan Monnier
2003-06-05  5:49       ` Eli Zaretskii
2003-06-05 10:58       ` Richard Stallman
2003-06-04 15:25 ` Eli Zaretskii
2003-06-04 15:47 ` Luc Teirlinck
2003-06-05 10:57 ` Richard Stallman
2003-06-05 12:27 ` Robert J. Chassell [this message]
2003-06-06  0:11   ` Kim F. Storm
2003-06-05 22:55     ` Miles Bader
2003-06-05 23:11     ` Robert J. Chassell
2003-06-05 23:23       ` Stefan Monnier
2003-06-05 23:56         ` Robert J. Chassell
2003-06-06  2:02           ` Miles Bader
2003-06-06 13:28             ` Robert J. Chassell
2003-06-06  9:50           ` Eli Zaretskii
2003-06-06 13:02             ` David Kastrup
2003-06-08  1:09               ` Richard Stallman
2003-06-08  1:20                 ` Stefan Monnier
2003-06-08  2:30                   ` David Kastrup
2003-06-09  8:53                   ` Richard Stallman
2003-06-06 14:00             ` Robert J. Chassell
2003-06-06 15:51               ` Eli Zaretskii
2003-06-06 16:54                 ` Robert J. Chassell
2003-06-06 17:25               ` Kevin Rodgers
2003-06-08  1:07               ` Richard Stallman
2003-06-15 15:47               ` Karl Eichwalder
2003-06-15 16:08                 ` Stefan Monnier
2003-06-15 22:27                   ` Miles Bader
2003-06-16 12:02                   ` Reiner Steib
2003-06-16 18:45                     ` Robert J. Chassell
2003-06-15 17:46                 ` Robert J. Chassell
2003-06-16  5:46                   ` Karl Eichwalder
2003-06-15 19:00                 ` Kai Großjohann
2003-06-06 17:24       ` Kevin Rodgers
2003-06-07 11:46         ` Kai Großjohann
2003-06-06 17:03   ` Richard Stallman
2003-06-05 16:50 ` Kai Großjohann
2003-06-05 20:50   ` Luc Teirlinck
2003-06-06 16:05     ` Luc Teirlinck
2003-06-06 16:29       ` Luc Teirlinck
  -- strict thread matches above, loose matches on Subject: below --
2003-06-09 23:17 Karl Berry
2003-06-11  0:24 ` Richard Stallman
2003-06-08 13:48 Karl Berry
2003-06-08 16:02 ` Eli Zaretskii
2003-06-09 23:00 ` Richard Stallman
2003-06-05 16:30 Karl Berry
2003-06-05 16:44 ` Luc Teirlinck
2003-06-05 23:39   ` Kim F. Storm
2003-06-06 17:03     ` Richard Stallman
2003-06-05 12:59 Karl Berry
2003-06-05 15:52 ` Luc Teirlinck
2003-06-05 16:23 ` Luc Teirlinck
2003-06-05 18:19   ` Luc Teirlinck
2003-06-06 17:02   ` Richard Stallman
2003-06-04 23:12 Karl Berry
2003-06-05  0:39 ` Luc Teirlinck
2003-06-04  8:54 Richard Stallman
2003-06-04  9:06 ` Miles Bader
2003-06-04 15:12   ` Andreas Schwab
2003-06-04 21:54     ` David Kastrup
2003-06-12  6:47       ` Karl Eichwalder
2003-06-12 22:13         ` Luc Teirlinck
2003-06-13  3:58           ` Karl Eichwalder
2003-06-13  5:00             ` Luc Teirlinck
2003-06-13  5:10               ` Luc Teirlinck
2003-06-13  6:16                 ` Stefan Monnier
2003-06-05  2:47     ` Kim F. Storm
2003-06-05 13:04       ` Andreas Schwab
2003-06-10  0:03         ` Kim F. Storm

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=m19NtqQ-000IetC@rattlesnake.com \
    --to=bob@rattlesnake.com \
    --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 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.