From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: [NTG-context] help wanted: English native speaker as co-editor
Date: Sun, 16 Apr 2023 20:49:53 +0200 [thread overview]
Message-ID: <4fd3b78f-7dec-2c03-70b5-fe83980f452b@fiee.net> (raw)
Hi, as most of you know, I’m the editor of context journal, the annual
magazine for all members of context group, AKA “proceedings of the
[previous] ConTeXt meeting”.
While I have some experience as an editor in German, my English is far
from perfect, so I need to rely on a native speaker for proofreading.
In the least years, Clyde was filling that role very diligently, but he
just moved and can’t make the time again.
Deadline for the current issue is only in August, but we’re already at
~100 pages with the articles I got (by Willi, Willi, Willi, Taco, Taco,
Götz, and me) and I’d like to spread the work a bit.
* Would you like to help with that? *
– You don’t need to understand the code.
– I want the text to be correct and understandable, we don’t need to
reach literary quality.
– You can work in PDF or in the sources, as you like.
– More than one person is welcome.
BTW I never thought of offering “our” articles to TUG and NTG, while I
sometimes got articles that were published in TUGboat or MAPS first.
(And I’m writing/translating for DANTE’s DTK regularly.) I’ll start to
do that, since “recycling” makes sense, and it also can’t hurt to spread
the word.
This is also a reminder to hand in your talks from Dreifelden – or new
articles!
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
reply other threads:[~2023-04-16 18:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4fd3b78f-7dec-2c03-70b5-fe83980f452b@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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.
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 NNTP newsgroup(s).