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:Software limitations From:geoff-h -at- MTL -dot- FERIC -dot- CA Date:Fri, 29 Aug 1997 08:24:29 -0500
How do you say that your software has limitations? My
passive-aggressive approach (when the omission bugs me too)
is to say "the current version of the software can't do X,
though future versions may", and hope that people will
write in and nag the developers to implement X. More
generally, I simply define the limits without drawing
attention to them. I don't consider it fair to let users
twist in the wind, wondering why they can't do something,
when all it takes is a few words to tell them they
shouldn't bother trying.
--Geoff Hart @8^{)} geoff-h -at- mtl -dot- feric -dot- ca
Disclaimer: Speaking for myself, not FERIC.
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
