![]() Their names are short and mnemonic to reduce typing, and when possible they are simply wrapped around the proofer text to avoid errors caused by removing characters. Macros in the working preamble are designed to minimize changes to the proofed text. ![]() Before you start formatting, please peruse the working preamble and project comments, and take care to format using the macros supplied. The working preamble can be found on the project page. Instead, every LaTeX project goes into the formatting rounds with a "working preamble", a set of project-specific macros designed to capture the semantic structure of the printed book. Each deficiency is fatal for easily-maintainable, high-quality ebooks of archival longevity.Įxperience has shown that no single set of simple guidelines will adequately handle even a majority of LaTeX projects. Unfortunately, visual markup suffers from two Great Flaws: It scatters formatting instructions throughout the document instead of centralizing them (making consistency all but impossible to achieve), and discards structural information (disparate structures are tagged with the same markup simply because their printed appearance is similar). Word processors are WYSIWYG by default, and visual markup is many people's first inclination for document encoding. Other structures are marked up analogously.īy contrast, visual markup, or WYSIWYG ("what you see is what you get"), dictates a document's appearance element by element, via explicit, low-level formatting instructions ("this text is italicized", "this heading is centered small caps"). The visual representation of chapters is controlled by modifying a single piece of information, the definition of the chapter tag. Instead of specifying the font weight and alignment of chapter titles (say), you mark each chapter with a dedicated "tag". Semantic markup, or WYSIWYM ("what you see is what you mean"), separates structural meaning from typographical appearance. In an ebook, these structures can be encoded or marked up either "semantically" or "visually". By nature, PPing is not distributed a single person must make stylistic decisions for the project as a whole.Ī printed book contains meaningful typographical structures: page numbers, chapter titles, running heads, figure captions, and so forth. After PPing, a book is ready for publication at Project Gutenberg (PG). The post-processor assembles the formatted content, ensuring consistency and coherency. Proofing and formatting are distributed processes-performed one page at a time by multiple volunteers per book, possibly over a period of weeks or months. Formatters add "tags" to specify how parts of the book will be presented visually. Proofers make typographical corrections, so the raw text matches the page scan. Important items (such as reminders to ask for human help) are repeated as necessary so they won't be overlooked by non-serial readers, and potential pitfalls are clearly marked.Ī book's contents go through three major stages at Distributed Proofreaders: proofreading ("proofing"), formatting ("F1 and F2"), and post-processing ("PP"). Section 3 constitutes a user's guide and reference manual, meant both to be read for tutorial information and to be thumbed through as you format your first pages.īoth parts are written in mostly-independent sections, culled from existing DP wiki pages, forum posts, and private discussions. Section 2 is a very brief introduction to DP, LaTeX, and their distinctive interrelationship. Frequently, where formatting decisions are concerned, you're directed to external resources (especially, writing to dp-feedback or posting in the forums). In the interest of brevity, this manual discusses only well-standardized, project-independent formatting, and cautions mostly against common errors. It's geared toward a variety of backgrounds: those who have proofed and formatted thousands of pages at DP but have always avoided LaTeX, long-time LaTeX users who are fairly new to DP and its ways, and (it is hoped) everyone in between. This manual contains guidelines for volunteers at Distributed Proofreaders who format projects using the typesetting language LaTeX. Before working on a LaTeX project in F1 or F2, please read the project comments carefully for detailed, project-specific instructions, and use the preamble code provided to test-compile each formatted page you check in. Instructions in project comments supersede these general guidelines. The printable manual is the primary source, and may be updated more frequently than this wiki page. This page is closely adapted from the August 2012 version of the printable DP LaTeX Formatting Manual. 3.1.3 Illustrations, Lists, Footnotes, etc.ĭistributed Proofreaders LaTeX Formatting Manual.1 Distributed Proofreaders LaTeX Formatting Manual.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |