Distributed Proofreaders 29 titles preserved for the world!
  DP
ID: Password:  ·  Register  ·  Help  
 

Post-Processing Verification Guidelines

Contents

General Procedures
Requests to Revise and Resubmit
Specific Checks to Make
Submitting a PPV Report Card

General Procedures

  1. Make all the checks you would make on a project you are post-processing.
  2. Keep track of all the corrections you make.
  3. Send the PPer a feedback note describing the corrections you made, and providing helpful hints for future work.
  4. Upload the project to PG.
  5. Submit a PPV report card.

Requests to Revise and Resubmit

Sometimes the PPer requests that they be allowed to make any necessary corrections and reupload the project for PPV. In this case, use the option on the project page to return the project to the PPer's queue, and send them an email or private message noting the items to be corrected.

Sometimes a PPVer may decide to ask the PPer to revise and resubmit. This is an optional decision on the PPVer's part; it is not required. If you feel it would be too time-consuming for you to make all the corrections necessary, or that the PPer would benefit from the experience of revising the project, ask the PPer to revise and resubmit, following these steps:

  1. Use the option on the project page to return the project to the PPer's queue.
  2. Send a private message or email to the PPer letting them know to expect the project to show up in their queue again, explaining the corrections that need to be made before re-uploading for PPV, and stating that if they do not wish/do not have time to revise, they can return the project to the PP queue so that someone else can work on it. Try to be as tactful and helpful as possible. Point them to posted projects to show them what the final product is supposed to look like. Provide links to relevant parts of the PP guidelines which they overlooked.

Specific Checks to Make

Check for the following types of errors, using tools you usually use for PPing:

Level 1 (minor errors)

  • Spellcheck errors
  • Scanno check errors
  • Comma/period error
  • Gutcheck errors
  • Jeebies errors
  • Extraneous characters, such as ~ ` + = | \ < > /
  • Ellipses not formatted according to guidelines
  • Ligature inconsistency (e.g., using [oe] and oe in same project, or ae and in same project when page scan uses all )
  • Italic markup incorrectly placed relative to punctuation
  • Inconsistently spaced initials
  • TOC not complete, or formatted inconsistently
  • Chapter heading inconsistency (# blank lines before/after; inconsistently centered or left-justified; inconsistently capitalized; period missing at end of chapter heading or subheading)
  • Footnotes/footnote markers missing or out of order
  • Improper joining or separating of paragraphs at page break
  • Hyphenated/non-hyphenated variants not addressed
  • Hyphen/emdash confusion (i.e., hyphen used instead of emdash, or emdash used instead of hyphen)
  • Emdash incorrect length
  • HTML - title tag not filled in correctly
  • HTML - Tidy-reported issues have not been addressed as necessary**

Level 2 (major errors)

  • Text not rewrapped to required line length
  • Rewrapping errors, e.g., rewrapped poetry
  • Poetry indentation not preserved
  • Markup (e.g., italic markup, blockquote/poetry indentation) removed
  • Missing page(s)
  • Printers' errors not addressed***
  • Improper placement of pagenum markup, if a TOC or index in the project uses page numbers (otherwise, placement of pagenum markup is not important)
  • HTML - invalid HTML (obviously not caused by a last-minute change to code)
  • HTML - invalid CSS
  • HTML - non-working links
  • HTML - filenames not in lowercase
  • HTML - images not in "images" directory
  • HTML - images not optimized

Other errors (not counted toward rating)

  • HTML - Not removing unused css

** When using Tidy, use the report mode, but do not allow Tidy to alter your code; instead, look at the report and make changes to your code as necessary.

*** Printers' errors should be addressed in one of the following ways:

  1. Correct silently
  2. Correct and note corrections in Transcriber's Note
  3. Leave uncorrected, and note errors in Transcriber's Note

"Not addressing printers' errors" means that all, or a large percentage, of printers' errors have been left uncorrected and not noted. If just one or two have been missed, and the rest addressed, then those missed would instead be counted as the relevant type of error (spellcheck, gutcheck, etc.)

Submitting a Report Card

Using the link on the project page, submit a report card for the project, using the following criteria for determing project difficulty and rating of PPer's work:

Determining whether a project is Easy, Average, or Difficult

Easy Project:

  • Straight fiction with little or no poetry
  • Straight poetry
  • Other straight text, e.g., essay
  • Can include illustration markup
  • No footnotes, no index, no blockquotes, etc.
  • 100 or fewer gutcheck flags
  • 100 or fewer spellcheck flags

Average Project:

Can include up to 3 of the following kinds of content:

  • poetry
  • blockquotes
  • footnotes
  • sidenotes
  • index
  • advertisements
  • tables

and/or:

  • 100-500 gutcheck flags
  • 100-500 spellcheck flags

Difficult Project:

Includes more than 3 of the following kinds of content:

  • poetry
  • blockquotes
  • footnotes
  • sidenotes
  • index
  • advertisements
  • tables

and/or:

  • 500+ gutcheck flags
  • 500+ spellcheck flags

and/or includes any of the following kinds of content:

  • multiple languages*
  • Englifh
  • musical notation/lilypond/midi files
  • extensive mathematical or chemical notation
  • LATex

* How to define multiple languages:

  • If the book is English on one page and Latin on the facing page, it counts as multiple languages.
  • If the author is travelling and repeatedly reports conversations in the foreign language of the country, it counts as multiple languages.
  • If extensive (paragraph or more) quotations in a language other than the base language are present, it counts as multiple languages.
  • If the Frenchman in the novel says "Zut!" a lot, it does NOT count as multiple languages.

Determining Allowable Errors for Various Ratings

Excellent

  • No Level 2 errors
  • If project is:
    • Easy
      • Up to 0.3 Level 1 errors/100k (or 1 error if file size < 300k)
    • Average
      • Up to 0.5 Level 1 errors/100k (or 1 error if file size < 200k)
    • Difficult
      • Up to 1 Level 1 error/100k (or 1 error if file size < 100k)

Good

  • No Level 2 errors
  • If project is:
    • Easy
      • Up to 0.6 Level 1 errors/100k (or 1 error if file size < 165k)
    • Average
      • Up to 1 Level 1 error/100k (or 1 error if file size < 100k)
    • Difficult
      • Up to 2 Level 1 errors/100k (or 1 error if file size < 50k)

Fair

  • May contain Level 2 errors
  • If project is:
    • Easy
      • More than 0.6 Level 1 errors/100k (or more than 1 error if file size < 165k)
    • Average
      • More than 1 Level 1 errors/100k (or more than 1 error if file size < 100k)
    • Difficult
      • More than 2 Level 1 errors/100k (or more than 1 error if file size < 50k)

Poor

Poor rating should be assigned at the PPVer's discretion, if it is felt that the project contains too many errors to be assigned a rating of Fair.

 
Copyright Distributed Proofreaders (Page Build Time: 0.003) Report a Bug