From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Major and minor modes
Date: Thu, 15 Jun 2017 08:10:21 +0900 [thread overview]
Message-ID: <D6524F3D-245C-449A-BC70-E0C2D4FCFBD3@gmail.com> (raw)
In-Reply-To: <41AE1409-13B6-404F-BE28-FE43D482360B@gmail.com>
As I just wrote, "That discrepancy is a bit weird." *especially* since the Info mode has groupings that don't even correspond to the PDF or the HTML...
I really think we should have more consistency in the way the manual is "visually" structured regardless of the format.
(And really, the 50+ pages of the "extra features" not being included in the 600+ pages manual *is* extra weird. If the issue were really to save on paper, we'd have a better balance between the manual and the extra features.)
Jean-Christophe
> On Jun 15, 2017, at 6:58, Jean-Christophe Helary <jean.christophe.helary@gmail.com> wrote:
>
>
>> On Jun 14, 2017, at 23:23, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>>> From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
>>> Date: Wed, 14 Jun 2017 12:49:21 +0900
>>>
>>> Interesting. I just noticed that the HTML and the PDF do not have the same chapter numbering.
>>
>> I think that's because the PDF version is produced like a printed
>> manual would be, which means some of the stuff is excluded, while the
>> HTML version includes everything, like the Info version would.
>
> It's different.
>
> 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
>
> So in the HTML, PDF sub-chapters are chapters on their own and the introductory text is not present:
> "This chapter explains the character sets used by Emacs for input commands, and the fundamental concepts of keys and commands, whereby Emacs interprets your keyboard and mouse input."
>
> PDF Chapter 3 "Entering and Exiting Emacs" corresponds to HTML
> • 5 Entering Emacs
> • 6 Exiting Emacs
>
> Then, until we reach PDF Chapter 31 "Miscellaneous Commands", everything corresponds and the HTML has introductory texts for each chapter just like the PDF.
> PDF 31 corresponds to HTML
> • 34 Gnus
> • 35 Host Security
> • 36 Network Security
> • 37 Document Viewing
> • 38 Web Browsing with EWW
> • 39 Embedded WebKit Widgets
> • 40 Running Shell Commands from Emacs
> • 41 Using Emacs as a Server
> • 42 Printing Hard Copies
> • 43 Sorting Text
> • 44 Editing Pictures
> • 45 Editing Binary Files
> • 46 Saving Emacs Sessions
> • 47 Recursive Editing Levels
> • 48 Hyperlinking and Navigation Features
> • 49 Other Amusements
>
> which were the subject of a recent discussion on emacs-devel btw.
>
> Then PDF has:
> 32 Emacs Lisp Packages................................. 431
> 33 Customization ...................................... 436
> 34 Dealing with Common Problems ....................... 468
>
> And that chapter 34 corresponds to HTML
> • 52 Quitting and Aborting
> • 53 Dealing with Emacs Trouble
> • 54 Reporting Bugs
> • 55 Contributing to Emacs Development
> • 56 How To Get Help with GNU Emacs
>
> That discrepancy is a bit weird.
>
> Jean-Christophe
next prev parent reply other threads:[~2017-06-14 23:10 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 [this message]
2017-06-15 13:33 ` Emanuel Berg
2017-06-15 15:05 ` Eli Zaretskii
2017-06-15 15:16 ` Drew Adams
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
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=D6524F3D-245C-449A-BC70-E0C2D4FCFBD3@gmail.com \
--to=jean.christophe.helary@gmail.com \
--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.
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).