 |
|
Title: Microsoft Manual of Style for Technical Publications
ISBN: 0735617465
Author:
Microsoft Corporation
Publicate Date: 2004-06-30
Publish: 2004-06-30
List Price: $29.99
Average Customer Rating: 4.0
Format: Paperback
 |
|
|
|
|
Amazon Lowest New Price: $14.63
Amazon Lowest Used Price: $14.72
Amazon Merchant Price: $19.79
|
|
|
|
|
|
|
|
|
|
|
| Customer Review: |
|
1: Excellent Manual...
...but not a proper textbook for undergraduate "Technical Writing" course. Definitely an excellent reference book for such course, though.
Dr. Sunil Samanta
|
2: MS Manual of style JFO Review
Book is excellent, delivery was ok, even if a little bit longer than expected.
|
3: Typical Microsoft
This book ok, but not great. Some of their standards are a little antiquated.
If you are a software tech writer, check out the Sun Technical Publications, Read Me First! A Style Guide for the Computer Industry, Second Edition.
If you work in the Mac world, then get the "Apple Publications, Style Guide." It is available free on the web.
|
4: Excellent document standards resource
We're using this one at work to help us write doc standards. It's invaluable! Thanks to Microsoft for recognizing that the term is "Web site" and that there is no such word as "website." Hooray!!
|
5: Serves a Specific Purpose
Honestly...I have been a technical writer for over 20 years and only recently even looked at this book. Granted, I found that how I learned to write was right on target. However, I think following this book to the letter is not a good idea. This book should be nothing more than a high-level reference for any "wannabe" tech writer. Technical writing is far more than proper capitalization (internet vs. Internet) or how you refer to something (dialog vs. dialog box). It's about your target audience, the message you're trying to convey, and the benefit to the end user. This book does not cover that: that comes from real world experience, training, and mentoring. I've seen too many people use this as their "bible" for technical writing when it shouldn't be.
As long as you keep in mind that this book will not teach you to be technical writer - only help bring continuity to your work allowing it to fall in line with others - then buy it.
|
|
|
|
|
