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: Sun, 20 Nov 2022 09:41:31 +0200 [thread overview]
Message-ID: <83y1s65az8.fsf@gnu.org> (raw)
In-Reply-To: <E1owYvn-00045N-Dy@fencepost.gnu.org> (message from Richard Stallman on Sat, 19 Nov 2022 20:15:35 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: rafaelbeirigo@gmail.com, 59258@debbugs.gnu.org,
> stefankangas@gmail.com
> Date: Sat, 19 Nov 2022 20:15:35 -0500
>
> > > 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.
>
> I know. But even if they are not about to reprint, we might want to
> suggest printing a newer edition corresponding to Emacs 29.
I'm not sure I understand. Are you saying that we should suggest to the FSF
to make a new printing, on our own initiative? If so, I don't think we are
aware of the FSF considerations for when they want to print the books again.
Every major Emacs release changes the manuals in fundamental ways, but does
the FSF indeed want to publish a new edition whenever a new major release of
Emacs is out (or maybe even when it's in final stages of pretest)?
next prev parent reply other threads:[~2022-11-20 7:41 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
2022-11-20 1:15 ` Richard Stallman
2022-11-20 7:41 ` Eli Zaretskii [this message]
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=83y1s65az8.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).