The Project Gutenberg FAQ 2002 — Inside the Classic

Historical Framing and Self-Awareness

Tinsley's preface immediately establishes the FAQ as a document of its time. He writes that Project Gutenberg 'doesn't have much written history itself,' and that pre-1996 materials have gone to 'the great bit-bucket in the sky.' This metaphor—colloquial yet vivid—signals a writer comfortable with technical jargon and informal register. The author does not claim omniscience; instead, he thanks proofreaders for corrections and accepts responsibility for remaining errors. This humility is a deliberate rhetorical choice, positioning the FAQ as a collaborative artifact rather than an authoritative decree. The historical lens also appears in the detailed account of early production challenges: the 'geometric' growth of output, the reliance on private e-mail, and the high volunteer turnover. Tinsley's diction—'painstaking,' 'significant amount,' 'serious challenge'—conveys the labor behind digital preservation without romanticizing it.

Technical Diction and Formatting Guidance

The FAQ's technical sections reveal Tinsley's attention to the materiality of text. In answering how to format letters or journal entries, he advises making them 'look like they are in the printed book,' with indented signatures and shorter lines for embedded letters. He distinguishes between scene breaks (which require asterisks) and new entries in epistolary works (which need only extra blank lines). The reasoning is practical: 'each new letter or journal entry cannot be mistaken by a careful reader.' This shows a nuanced understanding of typographic cues and reader cognition. Similarly, his discussion of the British pound sign—'cannot be expressed in ASCII, but is very common'—acknowledges the tension between character encoding and literary fidelity. Tinsley's voice here is instructional but not pedantic, using concrete examples like the Dracula excerpt to illustrate his points. The examples themselves are carefully chosen: a letter from H. Middleton and a journal entry from Renfield's asylum, both demonstrating formatting principles through recognizable literature.

Community Voice and Institutional Memory

Tinsley's acknowledgments and preface reveal a writer deeply embedded in Project Gutenberg's volunteer culture. He thanks 'all those who corrected my facts and my typos,' and singles out the 'Directors of Production'—Sue Asscher, Dianne Bean, John Bickers, David Price—as key community builders. The language is personal: 'They made a huge contribution to building community in PG.' This is not a dry FAQ but a document infused with gratitude and a sense of shared mission. Tinsley also describes the challenges of onboarding new volunteers, who 'showed up with great good will, but most of whom vanished after a week or two.' The phrasing is empathetic, not critical. Later, in the sections on the Literary Archive Foundation, the tone shifts to formal legal language—'501(c)(3) educational corporation,' 'tax exempt status'—but even here, the author inserts a personal note: 'U.S. laws alone swamp our small staff.' This blend of bureaucratic precision and colloquial exasperation is a hallmark of Tinsley's authorial voice.

Structural Choices and Reader Orientation

The FAQ's structure itself reflects authorial decisions about usability. Tinsley organizes answers by numbered sections (V.107, V.108), a convention that aids cross-referencing but also creates a sense of systematic coverage. He includes a preface, acknowledgments, and a detailed table of contents (implied by the numbering). The closing sections on the Foundation and donations are presented as appendices, yet they maintain the same question-answer format. This consistency suggests Tinsley views the entire document as a coherent whole, not a mere collection of tips. Notably, he does not include a conclusion or summary; the FAQ simply ends with the Foundation's contact information. This abruptness is a deliberate choice: the document is a reference tool, not a narrative. The author trusts readers to find what they need. The excerpts also show Tinsley's willingness to cite other FAQ entries (e.g., 'This is different from the case mentioned in the FAQ [V.102]'), creating an internal web of guidance that rewards sequential reading.

Tinsley's FAQ is best approached as a primary source on early digital volunteerism, not a polished manual. Readers should note the tension between its historical framing and its practical advice: the formatting rules are still useful, but the context of 2002—before widespread Unicode, before social media—shapes every answer. Pay attention to the author's voice: it is the voice of a community archivist, not a corporate writer. The FAQ rewards those who read between the lines, noticing what Tinsley chooses to emphasize (collaboration, gratitude) and what he omits (controversy, competition).

I keep thinking about how a catalogue is really a kind of love letter—to readers, to the carefully chosen words inside. This FAQ felt that way too, like tending a garden for strangers who might become friends. It reminded me of browsing Macmillan & Co.’s Catalogue. September 1874 Of Works in Belles Lettres, Including Poetry, Fiction, Etc. — Edition Insights, where each title whispered its own quiet promise, waiting for someone to pause and listen.