From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: rafaelbeirigo@gmail.com, 59258@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#59258: 28.2; [Emacs Manual] Available PDFs are outdated/obsolete
Date: Fri, 18 Nov 2022 10:27:05 +0200 [thread overview]
Message-ID: <831qq0d5wm.fsf@gnu.org> (raw)
In-Reply-To: <E1ovtZV-00055Y-3V@fencepost.gnu.org> (message from Richard Stallman on Fri, 18 Nov 2022 00:05:49 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: stefankangas@gmail.com, rafaelbeirigo@gmail.com,
> 59258@debbugs.gnu.org
> Date: Fri, 18 Nov 2022 00:05:49 -0500
>
> > AFAIU, these are the manuals that the FSF sells in their shop. I'd
> > rather not delete them, because when they decide to print another
> > edition,
>
> It would be good for the maintainers to talk with the FSF about when
> to publish a new paper edition.
It's usually the other way around: when the FSF is about to publish a
new version of some Emacs manual, someone from the FSF contacts us and
asks to produce a specially-formatted PDF file. They also show us the
colophon and the back-cover text and ask us to proof-read it for
factual mistakes; for example, the list of supported programming
languages and important features changes from edition to edition.
Because this happens once in a very long while, people tend to forget
what was done for previous printings, and that's why it is important
to keep the last printed book, so one could look inside and recollect
what was done and how.
next prev parent reply other threads:[~2022-11-18 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 20:18 bug#59258: 28.2; [Emacs Manual] Available PDFs are outdated/obsolete Rafael Beirigo
2022-11-15 3:20 ` Stefan Kangas
2022-11-15 13:40 ` Eli Zaretskii
2022-11-16 8:05 ` Stefan Kangas
2022-11-16 13:17 ` Eli Zaretskii
2022-11-17 10:38 ` Stefan Kangas
2022-11-18 5:05 ` Richard Stallman
2022-11-18 8:27 ` Eli Zaretskii [this message]
2022-11-20 1:15 ` Richard Stallman
2022-11-20 7:41 ` Eli Zaretskii
2022-11-23 23:16 ` Richard Stallman
2022-11-24 6:57 ` Eli Zaretskii
2022-11-29 23:50 ` Richard Stallman
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=831qq0d5wm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59258@debbugs.gnu.org \
--cc=rafaelbeirigo@gmail.com \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.com \
/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).