From: Marcin Borkowski <mbork@mbork.pl>
To: "Charles A. Roelli" <charles@aurox.ch>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Please help get ready for proofreading of Emacs manual
Date: Mon, 18 Sep 2017 22:10:36 +0200 [thread overview]
Message-ID: <87fubjepj7.fsf@jane> (raw)
In-Reply-To: <m2ingfn8i8.fsf@aurox.ch>
On 2017-09-18, at 20:53, Charles A. Roelli <charles@aurox.ch> 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
next prev parent reply other threads:[~2017-09-18 20:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 0:00 Please help get ready for proofreading of Emacs manual Richard Stallman
2017-09-18 18:53 ` Charles A. Roelli
2017-09-18 20:10 ` Marcin Borkowski [this message]
2017-09-19 19:33 ` Richard Stallman
2017-09-20 4:04 ` Marcin Borkowski
2017-09-20 20:35 ` Richard Stallman
2017-09-20 22:03 ` John Wiegley
2017-09-21 7:59 ` Eli Zaretskii
2017-09-21 14:26 ` John Wiegley
2017-09-18 20:27 ` Eric Abrahamsen
2017-09-18 23:36 ` Nick Helm
2017-09-19 3:56 ` Eli Zaretskii
2017-09-19 7:25 ` Petteri Hintsanen
2017-09-19 19:33 ` Richard Stallman
2017-09-20 18:50 ` Charles A. Roelli
2017-09-21 18:26 ` Richard Stallman
2017-09-19 19:33 ` 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=87fubjepj7.fsf@jane \
--to=mbork@mbork.pl \
--cc=charles@aurox.ch \
--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).