all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: RE: Major and minor modes
Date: Thu, 15 Jun 2017 08:16:16 -0700 (PDT)	[thread overview]
Message-ID: <1750a088-5dfd-4aba-8d45-1e013f587ed7@default> (raw)
In-Reply-To: <83bmpp2svz.fsf@gnu.org>

> > PDF Chapter 2 "Characters, Keys and Commands" has:
> > [introductory text about the chapter]
> > 2.1 Kinds of User Input
> > 2.2 Keys
> > 2.3 Keys and Commands
> >
> > but the HTML has:
> > • 2 Kinds of User Input
> > • 3 Keys
> > • 4 Keys and Commands
> 
> Ah, that...  It's because the manual does this:

<implementation considerations>

> IOW, a book requires somewhat different considerations wrt its
> sectioning than an on-line version of the manual.
>
> > That discrepancy is a bit weird.
> 
> Is it still weird?

Yes.  The PDF or print version of a manual should generally
have the same section numbers (and names) as an HTML or Info
or whatever else version.

It is fine for them to use different formatting.  It is even
fine if they have somewhat different text (e.g. xref text,
contextual paragraphs, whatever).

But section numbers, like section names, are not just content.
They are navigational.  They are used for reference, including
as was the case in this thread: someone pointing to a particular
section by name or number.

[Yes, a _link_ to a section in an online manual is often
preferable to such a purely textual representation.  But that
is not a reason why the section numbers or names should differ.]

As with everything, there might be exceptions.  But what was
shown here does not seem like a good candidate for being an
exception.

(Just one opinion.)



  reply	other threads:[~2017-06-15 15:16 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 23:58 Major and minor modes M.R.P.
2017-06-14  0:43 ` Jean-Christophe Helary
2017-06-14  1:49   ` Drew Adams
2017-06-14  3:49     ` Jean-Christophe Helary
2017-06-14  3:59       ` Emanuel Berg
2017-06-15  4:58         ` Marcin Borkowski
2017-06-14 14:23       ` Eli Zaretskii
2017-06-14 21:58         ` Jean-Christophe Helary
2017-06-14 23:10           ` Jean-Christophe Helary
2017-06-15 13:33             ` Emanuel Berg
2017-06-15 15:05           ` Eli Zaretskii
2017-06-15 15:16             ` Drew Adams [this message]
2017-06-16  2:09               ` Jean-Christophe Helary
2017-06-16  3:07                 ` Drew Adams
2017-06-16  4:44                   ` Emanuel Berg
2017-06-16  5:13                     ` Jean-Christophe Helary
2017-06-16  5:26                       ` Emanuel Berg
2017-06-16  6:59                   ` Eli Zaretskii
2017-06-16  8:02                     ` Jean-Christophe Helary
2017-06-16  4:34                 ` Emanuel Berg
2017-06-14  4:05     ` Emanuel Berg
2017-06-17 14:08       ` Narendra Joshi
2017-06-19  4:43         ` Krishnakant
2017-06-14  6:21     ` Krishnakant
2017-06-14  7:37     ` Phillip Lord
2017-06-14  1:54 ` Emanuel Berg
2017-06-14  7:40   ` Héctor Lahoz
2017-06-14  8:19     ` Emanuel Berg
2017-06-14  8:51       ` tomas
2017-06-14  9:25         ` Emanuel Berg
2017-06-14  9:36           ` Emanuel Berg
2017-06-14  9:58           ` tomas
2017-06-14 10:43             ` Emanuel Berg
2017-06-14 11:39             ` Emanuel Berg
2017-06-14 11:48               ` Emanuel Berg
2017-06-14 12:19               ` tomas
2017-06-14 14:15 ` Barry Margolin

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=1750a088-5dfd-4aba-8d45-1e013f587ed7@default \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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.