From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>, Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: version vs edition numbers in Emacs manuals
Date: Sat, 02 Nov 2019 09:59:41 +0200 [thread overview]
Message-ID: <83imo2k8sy.fsf@gnu.org> (raw)
In-Reply-To: <0d07699b-0b9f-fd44-11a2-9058c9eaa02b@cs.ucla.edu> (message from Paul Eggert on Fri, 1 Nov 2019 17:35:53 -0700)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri, 1 Nov 2019 17:35:53 -0700
>
> I noticed Glenn's comment at the start of doc/emacs/emacs.texi that
> EDITION (which was "Seventeenth") offers nothing that EMACSVER
> ("27.0.50") does not. I'd go further and say that it's a net minus,
> since it's confusing to have competing version numbers for the same thing.
>
> Although separating software version numbers from book edition numbers
> made sense in the old days when most users had only low-resolution
> displays and/or printers, nowadays the practice appears to be more
> trouble than it's worth. So I installed the attached patch, to switch
> the main Emacs manuals to simple version numbers like "27.0". Comments
> welcome.
I've reverted this.
We cannot unilaterally remove this stuff, we must talk to the FSF
publishing people and have their agreement first, because they will
need to know it is now their responsibility to keep track of the
edition number. The edition appears on the book's cover: e.g., my
copy of the latest Emacs Manual says "Eighteenth edition for GNU Emacs
version 26.1".
Richard, who we should talk to about changing this?
next prev parent reply other threads:[~2019-11-02 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 0:35 version vs edition numbers in Emacs manuals Paul Eggert
2019-11-02 3:07 ` Jean-Christophe Helary
2019-11-02 7:59 ` Eli Zaretskii [this message]
2019-11-02 17:23 ` Paul Eggert
2019-11-02 18:26 ` Eli Zaretskii
2019-11-03 3:26 ` Richard Stallman
[not found] ` <aa8429f8-34d2-e998-2bc6-7f7707b11ded@cs.ucla.edu>
[not found] ` <87h83brvxg.fsf@wjsullivan.net>
[not found] ` <0a820310-d4ce-d9ab-32b0-5d22c00d2122@cs.ucla.edu>
[not found] ` <87sgmvozz9.fsf@wjsullivan.net>
2019-11-12 19:32 ` Fwd: " Paul Eggert
2019-11-14 12:18 ` Eli Zaretskii
2019-11-14 19:42 ` Paul Eggert
2019-11-15 9:29 ` Eli Zaretskii
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=83imo2k8sy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@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).