Technical Book Review: "Microsoft Manual of Style for Technical Publications"

By Ugur Akinci

I love all kinds of writing but I’m especially passionate about technical communication and screenplay formats. In both genres I do have a good-sized library in my study. The technical communication side of my book collection is probably led by this fundamental volume that I’m known to have taken with me on a vacation or two:
Microsoft Manual of Style for Technical Publications

Enjoying its 3rd edition at this writing, this is a basic reference that ALL technical writers, novice or experienced, should have on their book rack and within easy reach.
The volume has two main sections: GENERAL TOPICS and USAGE DICTIONARY

GENERAL TOPICS (the first 199 pages) addresses many technical writing issues by TOPICS like “Indexing and Attributing”, “Web Cintent”, or “Content Formatting and Layout.

USAGE DICTIONARYY (pp. 200-380) is an alphabetical presentation of hundreds of technical communication terms, each followed by Microsoft’s recommendation how to use and/or write it (correctly and incorrectly), together with a correct punctuation guide is some cases. The “See Also” cross-references liberally peppering the volume increases the utility of each definition.
Here is an example:
—————————–

Table of Contents

root directory

Use this term, not home directory, to refer to the dictionary or folder (indicated in MS-DOS with a backslash: \) from which all other directories and folders branch. Do not shorten to root when you mean the directory.

Correct

Change to the root directory and type
edit autoexec.bat
See Also: directory; folder
—————————–
Besides its comprehensive coverage of a great number of technical communication terms and concepts, this volume has another practical use: settling various arguments and justifying the use of a certain style with which a text element is rendered. “Because Microsoft says so” is a justification I’ve used several times in my career to settle a dispute (successfully) because I sincerely believe that a lot of research and field experiencewent into every suggestion Microsoft makes in this manual.

Even if you are an Apple and Mac fan you should not let your platform and Operating System sympathies get in the way of owning a solid-gold reference book that will serve you well for years to come.
Highly and definitely recommended.

If you already own this volume, what’s your take? Do you agree that this is a must reference volume to have for all technical communicators? Please feel free to comment and share.

Posted in Books and tagged Books

About Ugur Akinci

View all posts by Ugur Akinci →

2 Comments

Gary Smith on March 14, 2011 at 3:42 pm

I own this reference guide but don’t consider it my definitive source for style and format. I’ve been a technical writer for 20+ years and have written extensively on the topic of style guide development. Knowing that many companies possess their own industry-specific style guides I do understand the need for a generic guide for those companies without their own guides. But I do not believe Microsoft is my leader in this field. For instance, working in the government I always default to the Government Printing Office Style Manual. GPO is used first and foremost for governmental agencies. And the publishing industry uses The Chicago Manual of Style, which I also prefer. Barring the existence of a company or other industry or academic guide such as UPI, AP, New York Times, or even the New York Public Library Style Guide, I would use Microsoft only third for technical publications, referencing GPO and Chicago respectively.

admin on March 16, 2011 at 9:03 am

I agree that “Government Printing Office Style Manual” is the one to use if you’re working for the U.S. federal government. Another excellent guide.

Gary Smith on March 14, 2011 at 3:42 pm

I own this reference guide but don’t consider it my definitive source for style and format. I’ve been a technical writer for 20+ years and have written extensively on the topic of style guide development. Knowing that many companies possess their own industry-specific style guides I do understand the need for a generic guide for those companies without their own guides. But I do not believe Microsoft is my leader in this field. For instance, working in the government I always default to the Government Printing Office Style Manual. GPO is used first and foremost for governmental agencies. And the publishing industry uses The Chicago Manual of Style, which I also prefer. Barring the existence of a company or other industry or academic guide such as UPI, AP, New York Times, or even the New York Public Library Style Guide, I would use Microsoft only third for technical publications, referencing GPO and Chicago respectively.
- admin on March 16, 2011 at 9:03 am
  
  I agree that “Government Printing Office Style Manual” is the one to use if you’re working for the U.S. federal government. Another excellent guide.