:Welcome:Welcome to DP, I hope you are enjoying the site. I have been looking at a few of the pages you proofed in the first round. You are doing very well! I didn't find any errors Congratulations!
:Welcome: Welcome to DP, I hope you are enjoying the site. I have been looking at a page you proofed in the first round. You are doing very well! I didn't find any errors! Congratulations!
:Welcome: Welcome to DP, I hope you are enjoying the site. I have been looking at a few of the pages you proofed in the first round. You are doing very well! Congratulations!
:Welcome: Welcome to DP, I hope you are enjoying the site. I have been looking at a page you proofed in the first round. You are doing very well! Congratulations!
:Welcome: Welcome to DP, I hope you are enjoying the site. I have been looking at a few of the pages you proofed in the first round. You have made a good start at proofing. Congratulations!
:Welcome: Welcome to DP, I hope you are enjoying the site. I have been looking at a page you proofed in the first round. You have made a good start at proofing. Congratulations!
:Welcome: Welcome to DP, I hope you are enjoying the site. I have been looking at a few of the pages you proofed in the first round. I fear that you are misunderstanding the purpose of Distributed Proofreaders. We are not trying to proofread (copyedit) books as though they are about to be published. At Distributed Proofreading, we are preparing books to be viewed online, and therefore much of our work is about making the text readable in a variety of browsers and programs. Picking out scannos - mistakes in the OCR scanning of the text is also an important aspect of proofing. So each page may end up looking a little different to its original image - but as long as the text is consistent with its author's intent, that's okay. Eventually, it will be one long page or file.
:Welcome: Welcome to DP, I hope you are enjoying the site. I have been looking at a page you proofed in the first round. I fear that you are misunderstanding the purpose of Distributed Proofreaders. We are not trying to proofread (copyedit) books as though they are about to be published. At Distributed Proofreading, we are preparing books to be viewed online, and therefore much of our work is about making the text readable in a variety of browsers and programs. Picking out scannos - mistakes in the OCR scanning of the text is also an important aspect of proofing. So each page may end up looking a little different to its original image - but as long as the text is consistent with its author's intent, that's okay. Eventually, it will be one long page or file.
:Welcome: Welcome to DP, I hope you are enjoying the site. I have been looking at a few of the pages you proofed in the first round. Thanks for volunteering! I see that you didn't make any changes to the pages that you proofed, but there were several things that should have been changed. I'm not sure why you didn't make these changes, but I will explain the changes that I made and where to find more about how to proof here at Distributed Proofreaders.
:Welcome: Welcome to DP, I hope you are enjoying the site. I have been looking at a page you proofed in the first round. Thanks for volunteering! I see that you didn't make any changes to the page that you proofed, but there were several things that should have been changed. I'm not sure why you didn't make these changes, but I will explain the changes that I made and where to find more about how to proof here at Distributed Proofreaders.
You are proofing hyphens correctly, rejoining the two halves of the word split at the end of a line with a hyphen.
Some words split with a hyphen at the end of the line are compound words and retain the hyphen when rejoined at the first line. Also be aware that many older texts had compound words that are now single words, especially to-day, to-night, and to-morrow.
You are proofing hyphens correctly, but you missed one. It helps to take a quick look along the right side of the page to look for hyphens. The spell checker also will spot hyphenated words that have not been rejoined, as long as the split word is not a compound word.
You are proofing hyphens correctly, but you missed some. It helps to take a quick look along the right side of the page to look for hyphens. The spell checker also will spot hyphenated words that have not been rejoined, as long as the split word is not a compound word.
Please retain line-breaks, you joined a few lines after clothing hyphens. Retaining line-breaks makes it easier for the 2nd round proofers and post processor to compare the image to the text. e.g.
Please treat em-dashes in the same way as hyphens. i.e. "clothe them if they are naked" at the beginning and end of a line. & Proof them as two hyphens.
Thanks for leaving the asterisk, it makes it easy for proofers in the later rounds to quickly find things you weren't sure about. In this case, I
You missed a few OCR errors. You might want to try using the spellchecker.
You missed a few end-of-page hyphenation marks:
and on the beginning of the next page:
should be proofed as:
and on the beginning of the next page:
This makes the hyphenation easy to spot for the post processing
software & it gets handled automatically. Please see the Guidelines
about end-of-page/beginning-of-page hyphenation at:
[url]http://www.pgdp.net/c/faq/proofreading_guidelines.php#eop_hyphen[/url]
While you understand the rule to rejoin the halves of a word split by a hyphen at the end of the line, we do not do that when the hyphenated word is at the end of the page. Instead, we only mark it by adding an asterisk (*) after the hyphen at the end of the page, and prefix the start of the next page with a hyphen.
So well done! You might want to try a few EASY or average projects if you haven't done so already. Or do a few more BEGIN pages (max. 25) if you would like some more mentor feedback. You can also request feedback from the second round proofer at any time by placing [** second round proofer please PM me with feedback, thanks ] at the top of the page. Another way to see what changes have been made to your pages in the next round of proofing is to click on "My Projects" at the top of the page in the Activity Hub or Welcome Page, and select the project. That will bring up the Project Comments page, and from there you can click on the "Just My Pages" to get the page detail page. It shows which pages got changed in the later rounds, and you can click on the "diff" link to see the changes. If you want to see what changes later proofers made to the pages you proofed in this book you can go to [url=]here[/url].
You might want to do a few more BEGIN pages (max. 25) if you would like some more mentor feedback. You can also request feedback from the second round proofer at any time by placing [** second round proofer please PM me with feedback, thanks ] at the top of the page. Another way to see what changes have been made to your pages in the next round of proofing is to click on "My Projects" at the top of the page in the Activity Hub or Welcome Page, and select the project. That will bring up the Project Comments page, and from there you can click on the "Just My Pages" to get the page detail page. It shows which pages got changed in the later rounds, and you can click on the "diff" link to see the changes. If you want to see what changes P2 proofers made to the pages you proofed in this book you can go to [url=]here[/url].
The best place to start is at the [url=http://www.pgdp.net/c/faq/faq_central.php]DP FAQ central[/url]. It has links to all of the things I'm mentioning below.
It may help you to print out the [url=http://www.pgdp.net/c/faq/proofing_summary.pdf]2-page Guideline Summary[/url] & keep it handy while you're proofing. It contains examples of text you will find in a project and the correct way to mark it up. While I recommend that you look over the entire proofing guidelines so that you will know what special circumstances need special proofing, I think the 2 page summary is more useful to the beginning proofer.
You can sample the DP Custom Proofing font at: [url]http://www.pgdp.net/c/faq/font_sample.php[/url] It is ugly, but using this font helps improve proofing accuracy.
Try the [url=http://www.pgdp.net/c/quiz/generic/main.php?type=step1&quiz_id=PQ]Proofing Quiz and Tutorial[/url] for a handy walkthrough of the Guidelines.
Don't forget to check out the [url=http://www.pgdp.net/phpBB2/index.php]Forums[/url].
Please respond to the [url=http://www.pgdp.net/phpBB2/viewtopic.php?t=6651]Feedback Poll[/url]. We appreciate your feedback!
If you want immediate advice on a DP question, or just want to talk to other people who are involved with Distributed Proofreading, check out [url=http://www.pgdp.net/phpBB2/viewtopic.php?t=5497&highlight=jabber]the links to Jabber (an instant messaging client)[/url].
I appreciate feedback on my feedback, so please let me know if you found this message helpful and understandable or otherwise.
Many thanks,
Bruce
When you find illustrations in the text, mark them like so:
See the Guidelines for more information about illustrations at: [url]http://www.pgdp.net/c/faq/proofreading_guidelines.php#illust[/url]
There was one illustration on a page embedded in a paragraph, when you
find one of these, place a blank line before and after the caption.
e.g.
should be proofed as:
Please see the Guidelines on Illustrations for more information: [url]http://www.pgdp.net/c/faq/proofreading_guidelines.php#illust[/url]
You were treated to a stealth scanno: [code][/code] should be proofed as: [code][/code] What's a stealth scanno? Find out at: [url]http://www.pgdp.net/phpBB2/viewtopic.php?t=1563[/url]
When you find poetry or epigrams, please add a blank line before the first line, and another blank line after the last line. [code][/code] See the Guidelines on Poetry at: [url]http://www.pgdp.net/c/faq/proofreading_guidelines.php#poetry[/url]
You missed an accented character: [code][/code] Use the drop-down tool in the Proofing Interface to cut and paste accented characters into the text window. See the Guidelines for more information on non-ASCII characters: [url]http://www.pgdp.net/c/faq/proofreading_guidelines.php#a_chars[/url]
Please leave the text as it appears in the image, even if it appears incorrect. If you find anything which you think is wrong, mark it with an asterisk to draw the attention of the 2nd round proofer and post processor. e.g.
Your biggest error in proofing is that you've misunderstood the bit
about removing extraneous spaces around punctuation. This does not
mean remove all spaces around all punctuation. It means that if
punctuation has spaces on both sides, remove the space on the side to
which it does not belong. For most punctuation, this means there
should be no space between the word preceding the punctuation and the
punctuation (e.g., no space between a word and a comma, period or
question mark, but the space after the punctuation is retained). For a
quotation mark, the extra space could either be preceding the
quotation mark (at the end of a quote), or after the quotation mark
(at the beginning of a quote). An example of an extraneous space is
the following line from one of your pages:
where there is punctuation on both sides of the punctuation (in this
case, a quotation mark). In this case we remove the space after the
quotation mark because it's at the beginning of the quote, like so:
And you landed a footnote. Please change any symbol markers to
asterisks (*), but leave numbers and letters alone.
The actual footnote should be proofed as:
See the Guidelines on footnotes at: [url]http://www.pgdp.net/c/faq/proofreading_guidelines.php#footnotes[/url]
Please remove the page header information at the top of the page:
Please see the Guidelines for more information on page headers: [url]http://www.pgdp.net/c/faq/proofreading_guidelines.php#page_hf[/url]
It may help you to printout the [url=http://www.pgdp.net/c/faq/proofing_summary.pdf]2-page Guideline Summary[/url] & keep it handy while you're proofing. It contains examples of text you will find in a project and the correct way to mark it up. While I recommend that you look over the entire proofing guidelines so that you will know what special circumstances need special proofing, I think the 2 page summary is more useful to the beginning proofer.
It is not necessary for you to add formatting to your pages in P1. In fact, it's strongly discouraged because we want you to concentrate on just checking whether the words and punctuation match the scanned image.
Please do not delete the formatting that was created by the content provider, as it will be used by the formatters when it gets to the F1/F2 rounds.
If you're not already doing so, I recommend that you use the spellchecker available in the proofing page. I consider myself a good speller, but it's caught a few scannos that I missed, so I now use it on every page. It also displays the text in a different font, which can help you spot punctuation errors or stealth scannos that might be correctly spelled words, but not correctly converted text for this image (like 'she' for 'the'). Some browsers, like Konqueror for Unix, and Safari for the Mac, have built in spellcheckers, and Firefox has the Spellbound extension. If you're using the browser's spellchecker, it's not necessary to use it and the proofing interface's spellchecker.
As you may be aware, DP recently changed the way projects are proofed. The first two rounds, P1 and P2, are supposed to concentrate on straight proofreading, making sure the pages were accurately recognized by the OCR program, fixing scan errors, and fixing minor items like rejoining hyphenated words at the end of line, and removing extraneous spaces around punctuation. Once you have proofed a number of pages, and passed a quiz showing you know the rudiments of our formatting guidelines, you'll be able to proof in the F1 formatting round. At some point, if you do well, and want the additional responsibility, you can request access to the P2 and F2 rounds, which are like the P1 and F1 rounds, but are meant to be meticulously scrutinized for errors. You are not required to do use a spellchecker in P1, or smoothread for stealth scannos, but if you want to qualify for P2, I advise that you do them anyway.
Please remove all spaces around hyphens or em-dashes. If the hyphen or p em-dash is at the beginning or end of a line (except at beginning or end of a paragraph), please join up both words on either side of the hyphen or em-dash at the end of the first line. Please see the Guidelines about dashes and em-dashes at: [url]http://www.pgdp.net/c/faq/proofreading_guidelines.php#em_dashes[/url]
Please remove spaces before any punctuation other than that a quotation mark that is the start of a quote. Please see the Guidelines about punctuations at: [url]http://www.pgdp.net/c/faq/proofreading_guidelines.php#punctuat[/url]