TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> Printing an entire web site (as I'll refer to the compilation of HTML
> that comprise the book) is not practical.
Actually, W3C's browser, Amaya, has a function called Make Book that lets
you compile and print a book from links.
Also, if you use cascading stylesheets, you can create a stylesheet
specifically designed for printed material.
I'm not saying that this makes HTML an ideal print medium. Far from it. But
if your primary goal is to have online documents that can be printed on rare
occasions, it's definitely workable for that.
> Is there a place for HTML. Of course. Is HTML a better format
> than PDF for
> making a printed book on-line. Absolutely not.
If that's the goal, you're right. But what I would ask is: Why? It seems a
little customer-hostile to provide a 'print' book and then say, "Oh, yeah,
you buy the paper and the toner and print it yourself." I realize this isn't
the only possible scenario for this, but it's one I've seen a few times.
I like PDFs for review copies, white papers, backups to printed manuals, and
so forth. For real hypertext, it's best to go with a hypertext medium, like