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.
Re: Microsoft Manual of Style vs. github.com/MicrosoftDocs/microsoft-style-guide
Subject:Re: Microsoft Manual of Style vs. github.com/MicrosoftDocs/microsoft-style-guide From:Chris Morton <salt -dot- morton -at- gmail -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 16 Aug 2018 15:49:42 -0400
I think it was Janice Gelb who always remarked that the *Sun Microsystems
Style Guide* (or whatever it was named) was far superior to that of M$ and
Apple. Much of it is probably still applicable, and I think you can likely
still turn up a copy (maybe through the Wayback Machine).
For the basics, one starts with CMoS or AP style, then looks to one of the
aforementioned guides in relation to step-writing and delineating GUI
elements.
In any event, everything mentioned herein is a *guide*, not a rule book.
The latter simply doesn't exist; if it did, it would likely be instantly
out of date upon publication. Here, I enjoy linguist (and a whole lot more)
Steven Pinker's thoughts about English construction.
In the end, if a client has its own style guide (e.g., IBM), then one
starts there.
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
