|
| 
| Author: Microsoft Corporation Publisher: Microsoft Press Category: Book
List Price: $29.99 Buy New: $19.79 You Save: $10.20 (34%)
Rating: 38 reviews Sales Rank: 31617
Media: Paperback Edition: 3rd Number Of Items: 1 Pages: 432 Shipping Weight (lbs): 5.2 Dimensions (in): 9.1 x 7.2 x 1.1
MPN: 9780735617469 ISBN: 0735617465 Dewey Decimal Number: 808.066005 UPC: 790145174659 EAN: 9780735617469
Publication Date: June 30, 2004 Availability: Usually ships in 24 hours
|
| Customer Reviews:
Useful and Resourceful July 12, 2001 14 out of 14 found this review helpful
I am a new-comer in the area of technical documentation. I recently joined a software company as a Technical Writer and am suddenly confronted with IT terminology usage, expressions and style issues. I sought refuge in this book (a concise glossary) and in its authority. I find helpful hints in these areas. But if your issue is HOW TO do DOCUMENTATION instead of style and terminology, you should go for 'Developing Quality Technical Information : A Handbook for Writers and Editors' by Gretchen Hargis (Editor), Ann Hernandez, Polly Hughes, Jim Ramaker.
Why is this book needed? February 14, 2006 13 out of 28 found this review helpful
A job I was recently working on used the Microsoft Manual of Style for Technical Publications as its style manual.
Now, as a Mac user I try to avoid Microsoft products, so you can imagine my displeasure when I realized -Microsoft published a style manual -I had to abide by it
I found it lacking and wrong. A good style guide doesn't require an editor to look elsewhere, but with the third edition just 398 pages, the Microsoft Manual of Style had me going to other resources numerous times (The Chicago Manual of Style's 15th edition, for example is 956 pages).
The goal of the book seems for Microsoft to justify all of the grammatical mistakes Word tries to push on users, such as its treatment of lists (p. 48): -always introducing them with a complete sentence or fragment followed by a colon -always starting each item with a capital letter -ending every entry with a period if "they all complete the introductory sentence or fragment"
The Microsoft Manual of Style, however, does get a lot of rave reviews on here, so maybe it does serve a purpose. It's universally agreed, however, that the included CD-ROM is useless (it wouldn't work at all on my PowerBook)
An essential reference for technical communicators May 31, 2000 12 out of 13 found this review helpful
If you've ever stumbled over technical word usage, such as "pulldown" versus "dropdown" menus or "choose" versus "select," this book is for you. It is yet another example of why Microsoft is at the forefront of software development: they make it easier for others to develop high-quality, Windows-compatible products. I rated this book so highly for two reasons. First, the dictionary format makes it very easy to look up words. Access is everything when you're in a hurry. Second, the information is presented effectively and efficiently--lots of visuals and examples with succinct explanations--just what you want in a book of this type. In short, it is an essential reference for technical communicators who write books and online help for Windows-based applications. Good luck trying to uphold standards without it.
Superb July 12, 2004 8 out of 9 found this review helpful
This third edition reflects the changes in the world of writing manuals, not just for print but also online (the web, online help, etc). While it's been a few years since the previous edition, Microsoft has made up for that by changing the book's format and including three "ebooks" on the CD (the style guide itself, Microsoft Computer Dictionary, and the Microsoft Networking Dictionary) that comes with the book.The previous edition had all subjects alphabetized, which has changed somewhat in this edition has changed that. The book's first part is devoted to alphabetized subjects (called the Usage Dictionary). However the book's first part is devoted to other writing topics, ones which the book's authors obviously felt deserved their own major sections. Subjects like "documenting the user interface," format and layout, global content, indexing, common style issues, grammar, and punctuation. All topics in the book's first part are discussed throughly. And topics not discussed in the first part are addressed alphabetically in Part 2 of the book titled the "Usage Dictionary." The book's Table of Contents lists each item in the Usage Dictionary for easy referral. I also liked how the authors recognized the changing world of documentation in the introduction where they point out how people using computers can be anyone from "home users," who use their computer for simple tasks, all the way to software developers, who produce programs for computers. While this is intended for writers documenting Windows software, it serves well on its own as an excellent style guide.
Serves a Specific Purpose December 17, 2006 8 out of 13 found this review helpful
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.
|
|
|
Copyright 2008 BetterEditor.net
| |