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.
Subject:Word 97 to Frame and Microsoft Bashing From:"George F. Hayhoe" <gfhayhoe -at- SCESCAPE -dot- NET> Date:Mon, 31 Mar 1997 09:20:43 -0500
Regarding the Word 97 to Frame question, Peter Gold noted:
<<Frame imports RTF nicely; has anyone tried this?>>
Apparently not; it's so much easier to complain about the
evil empire of Redmond. :)
I can't offhand think of a single software product that has
gone through half as many versions as Word and maintained a
single file format.
Why do file formats change? Why does anything change? It's
the price we pay for progress--in this case, new features
that the old file format cannot support.
What does all of this have to do with technical
communication? Not a whole lot on a superficial level, but
there's a kernel of relevant project management lore to be
discovered here. Never adopt new software products or
releases without analyzing the consequences of the change
on your current and prior projects, and planning your
It's not difficult to determine what your software
dependencies are (no, that's not a form of addiction!) and
to determine workarounds such as the one Peter suggested.
But it's generally much easier to do this before you commit
yourself or your organization to the new product or
release--when stress is minimal--than to install the new
product and find yourself with unanticipated compatibility
problems 24 hours before an important deadline.