all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: gregory@heytings.org, rpluim@gmail.com, stefankangas@gmail.com,
	emacs-devel@gnu.org
Subject: Re: feature/eglot-texi-manual 4725c123f3 2/5: ; eglot.texi: Fix typos and minor inconsistenciesfeature/eglot-texi-manual 4725c123f3 2/5: ; eglot.texi: Fix typos and minor inconsistencies
Date: Sun, 23 Oct 2022 22:21:52 +0300	[thread overview]
Message-ID: <83czaiqran.fsf@gnu.org> (raw)
In-Reply-To: <E1omgQB-0006mc-Hr@fencepost.gnu.org> (message from Richard Stallman on Sun, 23 Oct 2022 15:14:07 -0400)

> From: Richard Stallman <rms@gnu.org>
> Cc: gregory@heytings.org, rpluim@gmail.com, stefankangas@gmail.com,
> 	emacs-devel@gnu.org
> Date: Sun, 23 Oct 2022 15:14:07 -0400
> 
> We have made overall style changes many times in GNU manuals.  To do
> so for the whole Emacs Manual would be a big job, so we might not
> decide to do it, but it's not unreasonable in principle.

Such stylistic changes are at times a risky business: people don't
always understand the fine points of what the author wanted to express
or emphasize, and make changes for the worse.  This actually happened
in the past, and is not always easy to catch in time.  This is
exacerbated by the fact that the number of people we have who are both
native English speakers and are willing to invest a significant
portion of their free time in working on our documentation -- that
number is very small.

For this reason, my advice is to avoid stylistic changes, or at least
ask before making them.  It should be low priority anyway, since most
of our documentation problems are not of stylistic nature.



  reply	other threads:[~2022-10-23 19:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 10:38 feature/eglot-texi-manual 4725c123f3 2/5: ; eglot.texi: Fix typos and minor inconsistenciesfeature/eglot-texi-manual 4725c123f3 2/5: ; eglot.texi: Fix typos and minor inconsistencies Eli Zaretskii
2022-10-20 10:59 ` Stefan Kangas
2022-10-20 13:51   ` Eli Zaretskii
2022-10-20 11:35 ` Robert Pluim
2022-10-20 12:24   ` Stefan Kangas
     [not found]     ` <87a65qty8a.fsf@gmail.com>
2022-10-20 13:50       ` Eli Zaretskii
2022-10-22 19:59         ` Richard Stallman
2022-10-23  5:13           ` Eli Zaretskii
2022-10-23 13:19             ` Stefan Kangas
2022-10-23 16:18               ` Eli Zaretskii
2022-10-20 15:02       ` Stefan Kangas
2022-10-20 16:18         ` Eli Zaretskii
2022-10-20 20:34       ` Gregory Heytings
2022-10-20 22:35         ` Tim Cross
2022-10-21  6:04         ` Eli Zaretskii
2022-10-21  8:41           ` Gregory Heytings
2022-10-23 19:14           ` Richard Stallman
2022-10-23 19:21             ` Eli Zaretskii [this message]
2022-10-23 19:13         ` Richard Stallman
2022-10-20 15:11 ` Rudolf Adamkovič
2022-10-20 16:20   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83czaiqran.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gregory@heytings.org \
    --cc=rms@gnu.org \
    --cc=rpluim@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.