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.
The first five sound good. They ought to cover all the bases.
If your product is 100% compliant, I would put it on the front of the
package in large, bold, high contrast letters with one of those zig-zaggity
circles around it. (so I'm not even conversant as a graphic artist) :)
John
-----Original Message-----
From: Burns, Nancy [mailto:nburns -at- BREAULT -dot- COM]
Sent: Wednesday, September 16, 1998 8:46 AM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Y2K compliance - how to inform users
My company plans to advise customers (new and existing) about the Y2K
compliance of our software program. I'd appreciate your advice/suggestions
for ways to do this. For example, these are some of the ways we've thought
of:
Web site posting
Letter sent directly to current customers
Include letter in future shipments
Add topic to online Help
Include letter with pre-sales information
Add info to Getting Started manual
I'm not sure about the last one since it's not clear to me how the topic
fits within the scope of Getting Started. Do any of you include this
information in your manuals? Any thoughts - pros or cons - to any of the
above? Any other suggestions?
