On Sun, Feb 14, 2010 at 12:25 PM, Walter van Holst < walter.van.holst@xs4all.nl> wrote:
On 2/14/10 8:20 AM, Andrew Sly wrote:
And don't underestimate the role of the post-processor.
It still comes down to one person who has to do a lot of work on the text, and often make descisions about how to deal with many various things, before it is ready for submitting to PG.
What is it they actually do?
Regards,
Walter
_______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d
That's a simple question with a complicated answer. Here is an explanation <http://www.pgdp.net/c/faq/post_proof.php>that is apparently as concise as anyone has been able to come up with. As you can see, it's some mixture of: a.) validating all the work done by about 6 Rounds of work on each page in the project; b.) running a bunch of other semi-manual checks on the project; c.) filling the gap caused by the fact that the text markup and layout produced by the Rounds isn't the same as the text format and layout required by PG; d.) producing a complete HTML version of the project based on the format and markup that was originally considered appropriate for the text-only version that was all that PG offered at the time it was designed. So you can see that it's by far the majority of the individual tasks required to produce an e-book (text and html), only a small few of which have been distributed. In some cases the PPer also reproofs the entire project.