From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Please help get ready for proofreading of Emacs manual Date: Tue, 19 Sep 2017 15:33:22 -0400 Message-ID: References: <87fubjepj7.fsf@jane> Reply-To: rms@gnu.org NNTP-Posting-Host: blaine.gmane.org Content-Type: text/plain; charset=Utf-8 X-Trace: blaine.gmane.org 1505849629 8323 195.159.176.226 (19 Sep 2017 19:33:49 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 19 Sep 2017 19:33:49 +0000 (UTC) Cc: charles@aurox.ch, emacs-devel@gnu.org To: Marcin Borkowski Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 19 21:33:45 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1duOH9-0001tE-6R for ged-emacs-devel@m.gmane.org; Tue, 19 Sep 2017 21:33:43 +0200 Original-Received: from localhost ([::1]:45021 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1duOHG-0001KZ-6O for ged-emacs-devel@m.gmane.org; Tue, 19 Sep 2017 15:33:50 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37721) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1duOH3-0001IR-2d for emacs-devel@gnu.org; Tue, 19 Sep 2017 15:33:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1duOH2-0002zK-7q for emacs-devel@gnu.org; Tue, 19 Sep 2017 15:33:37 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:51693) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1duOGp-0002i5-8n; Tue, 19 Sep 2017 15:33:23 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1duOGo-0003Pq-QP; Tue, 19 Sep 2017 15:33:22 -0400 In-reply-to: <87fubjepj7.fsf@jane> (message from Marcin Borkowski on Mon, 18 Sep 2017 22:10:36 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:218536 Archived-At: [[[ 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. ]]] > But: should I check factual > correctness (for instance, whether the keys given really do correspond > to the command names in emacs -Q, or whether there are no mistakes in > command names)? (I assume yes.) Is there anything else? To do this efficiently, I suggest starting by reviewing the NEWS files for the past few Emacs major releases to recall what has been changed. You don't need to read the WHOLE NEWS file. Most of it, you can ignore. For instance, ignore the parts that don't affect the editing interface. Ignore the modes not covered in the Emacs manual, which is most of them. Don't try to remember all the details of what you see in NEWS -- just which areas have changed. Then, as you read and check the manual, if any of those areas comes up, you will notice it. At that point, refer to NEWS to double-check that the text is correct. You won't need to do that very often. > 3. In what format I should submit my corrections? (A simple diff/patch > might not be enough, since I might have a suggestion which may be > controversial and hence should be discussed. How would I mark such > places?) When it is a simple change, a diff is fine. You could send it as a bug report. I recommend sending only 5 such simple changes in one bug report -- then start another. It's only a matter of the maintainers' convenience. If you see a more complex issue, please write about it on emacs-devel. For complex issues, how you format your mail is not crucial, since the hard part will be thinking about the issue itself. -- 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.