diff --git a/www/contribute/producing-an-ebook-step-by-step.php b/www/contribute/producing-an-ebook-step-by-step.php index 97da3af1..ce54344a 100644 --- a/www/contribute/producing-an-ebook-step-by-step.php +++ b/www/contribute/producing-an-ebook-step-by-step.php @@ -536,10 +536,12 @@ proceed to seal up my confession, I bring the life of that unhappy Henry Jekyll
  • Missing thought or paragraph breaks. Is a paragraph unusually long? Does a scene change occur without <hr/>? They might have been lost during transcription.

  • Errors caused by the S.E. toolset. Tools like se british2american or even se typogrify can cause unexpected typography errors like quotation marks curled in the wrong direction, or dashes spaced incorrectly.

  • Archaic spellings. Is a particular word spelled in a surprising way? Mark it to check if it should be modernized. The Google Books Ngram Viewer is a great tool to get an idea of whether a word used to be spelled one way, but isn’t spelled that way anymore. Remember to change spellings in their own commits, prefaced with [Editorial]!

  • +
  • Printer’s errors. Before the computer age, hand-written manuscripts were sent to printers, whose job it was to lay the book out in lead blocks of type. During this process, the printer may have accidentally introduced their own typos, which are usually obvious errors in punctuation, spelling, or grammar. If you spot an obvious error like this that is present in both the transcription and the page scans, it may be a printer’s error that should be corrected in an [Editorial] commit.

  • There are some things that you don’t have to worry much about when proofreading: