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.
Bill, I've never heard of *writing* style that is mandatory in documenting
Windows PC software. Readable is good.
I have encountered a Style Guide that is a Microsoft standard and highly
recommended for others...but it refers to what various doohickies are called
and such. Is that what you meant?
In article <m0t8H0G-0001VyC -at- fisc>, William -dot- Hartzer -at- emc2-tao -dot- fisc -dot- com says...
<a developer> insists that there is a specific type of writing style that
must
be used when documenting a Windows PC software product.
<snip>
>Also, is there such a thing as a writing style that must be used whenever
>Windows PC software products are being documented? This developer claims
>that this Windows PC software product writing style is MUCH different than
the
>writing style I'm supposed to use when documenting an IBM Mainframe product
>or even a Macintosh software product.
