From: Richard Stallman <rms@gnu.org>
To: charles@aurox.ch (Charles A. Roelli)
Cc: emacs-devel@gnu.org
Subject: Re: Please help get ready for proofreading of Emacs manual
Date: Tue, 19 Sep 2017 15:33:22 -0400 [thread overview]
Message-ID: <E1duOGo-0003NK-0L@fencepost.gnu.org> (raw)
In-Reply-To: <m2ingfn8i8.fsf@aurox.ch> (charles@aurox.ch)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> The following parts may not all need to be proofread:
> Part 32
> The GNU Manifesto ..................................... 544
That's right. This is unchanged.
> Part 33
> Glossary...............................................552
That one should be checked, if it has changed since Emacs 21.
> Part 34
> Key (Character) Index ................................... 575
> Command and Function Index............................. 585
> Part 35
> Variable Index.......................................... 599
> Concept Index.......................................... 607
The indices need to be checked in two special, simple ways:
* Looking for items that are too long (so they mess up the formatting).
* Looking for items that are effectively duplicates.
If they start with the same word and go to the same page,
usually one should be deleted (but not absolutely always).
Here's an artificial example:
string constant ......................................42
string ...............................................42
Also, multiple pages for the same topic might mean one should be
deleted, keeping the one that gives the full explanation of that
topic.
Also, there can be spelling errors in the index as anywhere else.
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
prev parent reply other threads:[~2017-09-19 19:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 0:00 Please help get ready for proofreading of Emacs manual Richard Stallman
2017-09-18 18:53 ` Charles A. Roelli
2017-09-18 20:10 ` Marcin Borkowski
2017-09-19 19:33 ` Richard Stallman
2017-09-20 4:04 ` Marcin Borkowski
2017-09-20 20:35 ` Richard Stallman
2017-09-20 22:03 ` John Wiegley
2017-09-21 7:59 ` Eli Zaretskii
2017-09-21 14:26 ` John Wiegley
2017-09-18 20:27 ` Eric Abrahamsen
2017-09-18 23:36 ` Nick Helm
2017-09-19 3:56 ` Eli Zaretskii
2017-09-19 7:25 ` Petteri Hintsanen
2017-09-19 19:33 ` Richard Stallman
2017-09-20 18:50 ` Charles A. Roelli
2017-09-21 18:26 ` Richard Stallman
2017-09-19 19:33 ` Richard Stallman [this message]
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=E1duOGo-0003NK-0L@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=charles@aurox.ch \
--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 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).