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.
PS: Yes, I can spell "imminent". I just can't type it.
> -----Original Message-----
> techwr-l-bounces+kevin -dot- mclauchlan=safenet-inc -dot- com -at- lists -dot- techwr
inc -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of McLauchlan, Kevin
> Sent: Wednesday, January 28, 2009 10:11 AM
> To: John Cook; techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: RE: How do I document vaporware?
> John C replied in jest, but I think that that might actually be the
> best approach.
> Others noted that leaving the broken features in the
> interface is a form
> of "promise to perform", but I will point out that "a future
> release" is
> not any kind of specific promise about "the very next release"... So
> it's not that iminent.
> Where you WOULD (IMHO) run into that kind of difficulty is if you
> document them as you currently think they are going to work, and then
> that changes when the features finally get implemented.
> Instead, the blank page or a nearly-blank page (lots of white
> space) and
> a standard:
> " - Possible future feature. Funtionality not established. - "
> And then pointers to what other folks suggested about workarounds or
> "You can't get there from here."
> For purposes of place-holding, you could always document the way a
> feature is supposed to work, then hide the text.
> - Kevin
> > -----Original Message-----
> John Cook replied:
> > Sent: Tuesday, January 27, 2009 9:42 PM
> > To: techwr-l -at- lists -dot- techwr-l -dot- com
> > Subject: Re: How do I document vaporware?
> > Blank pages. Obviously. ; )
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-