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.
One word of warning: there are few things more frustrating than
an almost-WYSIWYG display. We have an SGML-based publishing
application here (I don't think the root of the problems is
in SGML, though), which includes a "preview" function designed
to show you what your page will look like. I had something
recently, involving a string of italicized terms separated by
the Unix pipe symbol |, and when I previewed it, it looked as
though my line was too long. After much effort, I squeezed it
down to fit, and triumphantly printed. The page that had looked
right on screen turned out, when printed by the same software,
to have an _underfull_ line. When I took out all the fixes I
had patiently put in, and ignored the preview function, the
page worked. The only explanation I ever got for this was "it
isn't wysiwyg," which is literally true--what I saw wasn't
what I got--and misses the point, because the only purpose of
a page previewer is to be wysiwyg.
Vicki Rosenzweig
vr%acmcr -dot- uucp -at- murphy -dot- com
New York, NY
