-
Notifications
You must be signed in to change notification settings - Fork 13
HowTo Proofreading
All Langsci books undergo Community proofreading. It is the series editors' responsibility to assure that their field is adequately represented among the proofreaders.
The following phases are distinguished:
- recruitment
- assignment
- distribution
- correction
- collection
- reminders
- forwarding
- tracking
- acknowledging
The list of proofreaders is available from http://langsci-press.org/groupMail
The following message is sent out to the proofreaders. All are put in BCC
Dear proofreader,
you are registered with Language Science Press as a proofreader. The
next book is about to reach proofreading stage. As you know, Language
Science Press depends on the community to help in the creation of our
books. We would therefore like to ask you if you could proofread one or
several chapters of the following volume
"**$title**"
by **$author**
The book has **$i** chapters with **$p** pages altogether and two sample texts.
Please let us know whether you would find some time for proofreading
until **$duedate**, and if yes how many pages you would be
willing to take on.
As always, proofreaders are acknowledged in the colophon of books and
also in our Hall of Fame (http://langsci-press.org/about/hallOfFame).
Best wishes
Sebastian
**$bookurl**
**$blurb**
**$chapterlist**
Offers for proofreading are collected between Monday and Wednesday. Proofreaders can expect preferences for a certain length or a certain topic.
On Wednesday, assign the proofreaders to chapters, taking into account their preferences, their native language, and their expertise. Ideally, each chapter should be covered twice. Proofreaders can be sloppy or fussy. Chapter should not be given exclusively to proofreaders known to be sloppy.
Run make proofreading . This creates the file proofreading.pdf, which is stamped as a preliminiary version not for circulation
run make versions.json followed by make paperhive. This will put the proofreading.pdf on paperhive.
Run make chapterlist to get a list of all chapters. Clean this list and paste it into the file chapternames
Copy the assignments from the spreadsheet into assignments
Run python assignproofreaders.py 123 Smith where 123 is the github-ID and Smith is the name of the first author.
This will generate mails for all proofreaders. Adapt the email addresses and send.
Proofreaders generally have four weeks. There is little purpose in giving them longer, as this will only make them start later. Correction can be done via pdfcomments, a separate text file or via Paperhive. This is up to the proofreader, but Paperhive is preferred on our side.
Proofreaders will inform the coordinator when they are finished.
Several days after the due date, proofreaders who have not yet turned in their corrections are sent a reminder.
Authors have a choice of receiving the corrections as they come in or in bulk when all are there.
With https://github.com/langsci/pypi/blob/master/langsci/standalonescripts/proofreadingdensity.py you can see the level of coverage of the book
https://github.com/langsci/shellscripts/blob/master/getproofreaders.sh gives a list of all commenters for a given LangSci ID. Complement this list with all proofreaders who sent their corrections via email or other means.