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.
See, this proves my point in how Microsoft really believes they now control
manuals as well. First, this seems unethical. (I want to say illegal, but it's
too strong a word although it feels like it's more appropriate.) Can Microsoft
really determine the language and terminology used because they've made the
program? And, if they can, then maybe they should just have their technical
writers come up with some generic documentation and everyone who's getting a
Microsoft Certified software program can sack their technical writers. I feel
sorry for the end users who are going to be using the GUI and stumble on
language because it's now Microsoft-speak...how Big Brother of them!!
I forgot to mention Strunk and White's Elements of Style. Ah to remember the
good old days when we used to be writers and trusted to write!
>I am preparing a proposal for Microsoft, and from informal talks with
>Microsofties, it is clear that if you want a Microsoft Certified software
>program (so the logo can be carried on the package), you better follow as
>many ofd their guidelines as possible. Especially when it comes to the GUI
>used in the application.
>I still prefer the Chicago Manual Of Style.
>>Has everyone out there lost there minds!! Does anyone remember when REAL
guides were used (Chicago Manual of Style, etc.)? I hate to remind
but the Microsoft Manual of Style is nothing more than a style manual taken
an in-house technical writing department that was published because that
in-house technical writing department happens to be MICROSOFT!!