here's a copy of a list i made in a post from october of 2004
-- that's right, october of _2004,_ more than 8 years ago --
explaining the workflow of the infrastructure i'd suggested:

1.  the e-texts -- as they are now -- must be regularized.
2.  i can write programs to do most of that automatically.
3.  the results need to be checked for quality control, and
4.  some missing information will need to be re-inserted.
5.  once that is done, the files will be _finished_, in that
6.  my viewer will present them as high-powered e-books.
7.  users can push a button to create high-end .html files,
8.  or save text as an .rtf file, or print out to paper or .pdf,
9.  in a way that gives 'em customized high-quality output.
10.  my program will do text-to-speech, and screenshots,
11.  and let people explore the project gutenberg library,
12.  and easily report errors they encounter in any e-text.
13.  those error-correction reports will be automatically
14.  routed to a system that presents all the material, so
15.  a human only has to say "yes" to approve the mod, and
16.  change-logs will be updated and a notice distributed.
17.  this e-text standardization and ease of handling will
18.  nurture a flowering of synergistic uses of the library
19.  by an array of creative and imaginative programmers
20.  that will engender a book-driven revolution in thought.
21.  and everyone will live happily ever after.  the end.

still seems like a good plan to me...  then again, who cares?

-bowerbird