From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Marcin Borkowski Newsgroups: gmane.emacs.devel Subject: Re: Please help get ready for proofreading of Emacs manual Date: Mon, 18 Sep 2017 22:10:36 +0200 Message-ID: <87fubjepj7.fsf@jane> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1505765467 20578 195.159.176.226 (18 Sep 2017 20:11:07 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 18 Sep 2017 20:11:07 +0000 (UTC) User-Agent: mu4e 0.9.19; emacs 26.0.50 Cc: rms@gnu.org, emacs-devel@gnu.org To: "Charles A. Roelli" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 18 22:11:02 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 1du2Nh-00051m-SA for ged-emacs-devel@m.gmane.org; Mon, 18 Sep 2017 22:11:02 +0200 Original-Received: from localhost ([::1]:38734 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1du2Nn-0004vF-Iy for ged-emacs-devel@m.gmane.org; Mon, 18 Sep 2017 16:11:07 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47250) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1du2Nc-0004uR-TW for emacs-devel@gnu.org; Mon, 18 Sep 2017 16:10:57 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1du2NX-0007AV-IN for emacs-devel@gnu.org; Mon, 18 Sep 2017 16:10:56 -0400 Original-Received: from mail.mojserwer.eu ([195.110.48.8]:47649) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1du2NX-00079x-6X; Mon, 18 Sep 2017 16:10:51 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by mail.mojserwer.eu (Postfix) with ESMTP id 36B13E6C0D; Mon, 18 Sep 2017 22:10:49 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.mojserwer.eu Original-Received: from mail.mojserwer.eu ([127.0.0.1]) by localhost (mail.mojserwer.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q_1bhgPdxUwS; Mon, 18 Sep 2017 22:10:45 +0200 (CEST) Original-Received: from localhost (static-dwadziewiec-jedenpiec7.echostar.pl [109.232.29.157]) by mail.mojserwer.eu (Postfix) with ESMTPSA id 91EE3E6C04; Mon, 18 Sep 2017 22:10:45 +0200 (CEST) In-reply-to: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.110.48.8 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:218489 Archived-At: On 2017-09-18, at 20:53, Charles A. Roelli wrote: > Here's a start, based on a recent build of the Emacs manual (644 > pages). "LONG" parts may still be further split, "SHORT" parts > combined. I could take one of the "Long" parts. (I'd like especially to do part 15, since I edit documents in natural languages in Emacs _a lot_, but part 16 would also be nice - I also happen to be a programmer.) While I am fairly busy now, this is kind of work I do like a lot and I will gladly do it in my spare time. (Also, I've been doing proofreading professionally for a journal for about 10 years now, though not in English.) I'd consider it also a way to give back to the Emacs devs for the great work they have been doing for the last four decades. What I absolutely _must_ know beforehand, though, is: 1. How much time do I have for this task. 2. What exactly should I pay attention to? I assume that the most important things to look for are parts which are impreciseor difficult to understand, not ordinary typos. 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? 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?) I think these questions are relevant to other proofreaders, too. Best, and I'm really looking forward to this job. -- Marcin Borkowski