2 ms·
The bottleneck at PGDP these days is not actually proofreading texts or even marking them up, but "post-processing" them - going from a bunch of proofread and m
by zozbot123 8y ago
The bottleneck at PGDP these days is not actually proofreading texts or even marking them up, but "post-processing" them - going from a bunch of proofread and marked-up page texts (and the original page images) to a complete HTML edition, ready for posting at Project Gutenberg. Many projects run aground at this stage, because they have relatively few contributors for that sort of work. So, if you really want to help (and have relevant skills), you should ask about taking over some old projects that are stuck in that state.
- fernly 8y agoAll of PGDP is fun and satisfying volunteer work if you like reading, but the Post-Processing stage was for me, the most fun of all. However, in order to qualify as a PPer you must first put in a rather lengthy apprenticeship working in the different levels of proofing. PGDP FAQ: https://www.pgdp.net/wiki/DP_Official_Documentation:General/FAQ_Central https://www.pgdp.net/wiki/DP_Official_Documentation:General/... PGDP Post-Processing FAQ: https://www.pgdp.net/wiki/DP_Official_Documentation:PP_and_PPV/Post-Processing_FAQ https://www.pgdp.net/wiki/DP_Official_Documentation:PP_and_P... > On its journey through multiple proofreading and formatting rounds, the text may have been worked on by hundreds of volunteers. Post-processors must standardize the formatting of the book and adjust it to comply with Project Gutenberg's requirements. They must also deal with any detectable mistakes or inconsistencies that have survived all proofreading and formatting rounds. > The ultimate goal of post-processing is to create a consistently formatted etext, that contains as few errors as possible and that accurately reflects the intentions of the author.