Producing properly formatted text for the WebBook required a different approach. New developments such as Dynamic HTML and Cascading Style Sheets have improved upon HTML's heretofore limited formatting capabilities. But these approaches amount to sharing responsibility for formatting between the author and the reader. If the author wants to make sure that the user sees his document formatted exactly as he intended, more drastic measures are called for. My choice, and in my opinion the only choice with today's technology, was to require the reader to use the Adobe Acrobat Reader, which required me to use the Adobe Acrobat PDFWriter to prepare the PDF files required by the Reader. To prepare the fully formatted documents for processing by the PDFWriter, I used Microsoft Works, whose word processor is a stripped-down version of Microsoft Word. I like its Easy Formats tool, which keeps the most recently used formatting tags in a short menu for rapid access, while still allowing ready access to less commonly used tags from a longer menu. For several of the later chapters, I switched to Microsoft Word, even though it had no significant advantages over MS Works, at least for this project. For most other publishing projects, I have now switched to Adobe's new InDesign program, whose only real advantage for non-graphical documents like Foundations is that its line-breaking algorithm considers the appearance of the entire paragraph when deciding where to end each line of text.