Customer Reviews

Microsoft Manual Of Style For Technical Publications (Second Edition)

5 star:		(12)
4 star:		(6)
3 star:		(0)
2 star:		(0)
1 star:		(3)

 

 

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.

Already a popular tome with software documentation professionals, this new edition has much to offer both to the new reader and those who have read the previous version cover to cover.

Modestly informing its readers that only 17 heavily revised or new terms have been included in this publication, the new Microsoft Manual of Style for Technical Publications has nonetheless expanded its overall topic list by a total of 144 entries. This has increased the size of the book from the previous edition by 44 pages. Many outdated and unused terms have been taken out of the manual, only to be updated to include significant changes in Internet and browser terminology and usage.

From a presentation standpoint, there are minor changes to the headings and body text. Of particular note however is the new alphabetical tabbing appearing on the outer edge of the document to help locate the topics. The index is structured to contain more subentry references as well. Gone however is Appendix C, the Words with Numbers section.

As with the earlier edition of the manual, this copy contains a standard Windows Help system version of the book. To demonstrate support of its new HTML-based Help standard however, Microsoft has also enclosed the same information on an HTML Help system (what it refers to in the manual as an "electronic book"). For additional incentive, there is also an HTML Help version of the third edition of the Microsoft Press Computer Dictionary - another helpful resource. Be aware though that to view these HTML materials you need to use Internet Explorer 4.0 or later (also included on the companion CD).

As more software development companies are designing applications that use browser technology or can be accessed via the Internet and World Wide Web, the new topic information this book contains is timely. Other new and enhanced terminology is also extremely beneficial.

- Mike Donoghue, AMS Services (donoghmi@amsworld.com)

This is an outstanding publication for anyone who uses Microsoft products, particularly Word.

The genius is in its simplicity. Organized alphabetically, with tabbed pages, the index is almost unnecessary. The two Appendii, "List of Acronyms and Abbreviations" and "Special Characters" are helpful, but probably won't get much use here. A CD-ROM comes with the book, but it's faster to pick up the book and go straight to the information you need. (I love books.)

The information is comprehensive, easy to find, easy to read and understand. Several screen shots "show, don't tell". Bonus: there's plenty to disagree with.

Even though it is thoroughly Microsoftesque, it probably will become the standard which serious computer users rely upon. Professionals and novices can use this book on a daily basis. There's a great education in this book. I wish I had written it.

It not only covers the basics (grammar, punctuation and the like), but standardizes many terms and functions relating to computers, the Web, Help systems--even ordinary documents. Macintosh computer users will find great information here, too.

If you want your work to look good, this book should be on your desk.

Reference and more. Useful. But there is a quaintness to some of its opinions. For example, "multitasking" is not to be used as a verb ("it is jargon"), do not say "grow your business," do not use "peripheral" as a noun, to refer to computer accessories, etc. My favorite entry, especially fun to find in light of Microsoft's legal problems arising in part from its relationship to Netscape Navigator, is this Orwellian directive, found on p. 185: "Navigate. Avoid the verb 'navigate' to refer to moving from site to site, page to page within a site, or link to link on the Internet.(...) Instead, use 'explore' to mean looking for sites or pages generally..."

A useful book in many ways.

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.

Recently:

The bible of style for IT. Many corporations need something like this to create a style guide. I reviewed this manual a few years ago for Amazon and for Microsoft.

The third edition is now several years old, and it shows. It shows the aches and pains of teenage angst. It hardly knows the Internet exists. It joins the AP and Chicago manuals of style in thinking e-mail must be hyphenated, for example, when convention abandoned such proper use a long time ago.

However. However, as the only bible for the IT industry, the Microsoft manual is extremely helpful. It is the only independent, arbitrary judge to resolve prickly spelling and punctuation issues not easily found from a single, authoritative source online. This means it is often the only arbitrary judge. That the fact that Microsoft is the author often doesn't sit well with IT professionals who make hating Microsoft a occupational trait. But Linux or Macromedia don't have manuals of style for IT. Nobody else does. So this also means that the guide is extremely useful for checking:

* Do's, don'ts and alternatives for using technical terms
* Best practices for writing and tagging Web content
* Dialog boxes and error messages
* Standards for accessible communications
* Fast answers on proper spelling, grammar and punctuation

It provides a universal grammarian for technical publications:

* Formatting Content and layout
* Content for software developers
* Indexing and attributing
* Common style problems
* Grammatical elements
* Punctuation

The manual defines standards and best practices for technical writers, editors and content managers from accessibility and globalization issues to mobile computing, XML as well as Microsoft-specific products, technologies, and initiatives; writing for software developers. The manual helps maximize the impact of technical communications. It also has a section just for software developers.

I got my copy a few years back. I still it check about once a day! I mark my copy each time I look up a word or a term (Wikipedia is more thorough, but it is not a IT style book). Most pages have at least one mark. After all, who remembers if "log on" as a verb is two words, while login as a username is one? Plus it helps with IT professionals who say every screen shot is a window and that all boxes are PCs. NOT.

Years ago:
For technical writers with anything to do with computers, this is the book. There are not too many to choose from anyway and this one is well organized, authoritative, not too expensive and very useful. Rather than re-iterate the points already made, I would like to add:

Version three of this blue cover book was copyrighted in 1998, so while it is extremely useful in setting departmental or corporate standards for thousands of computer terms, it is already slipping behind the steady stream of new computer words. Perl, for example, is a popular language for the Internet and while it is an acronym, it is not capitalized. The MS manual does not mention it.

Microsoft does indeed have many manuals published through its MS Press publishing arm and this manual clearly sets out exactly what their word style and use should be. This makes the manual some of what it claims to be (" a standard reference for technical writers"). It would not be enough however, for editors and journalists (another of its claims). For writing professionals, the weighty Chicago manual is irreplaceable as the style standard - the MS Manual is useful as a computer word companion.

I recommended this manual as a standard setting guide for our company and it has been a quite useful and inexpensive tool. At first, the book was used several times a day. Now, almost a year later, it is still opened about once a week. (E-mail is hyphenated, PING is an acronym.) Especially useful are the proper names for all the parts of windows, screen, buttons, etc.

The CD version included with the book is not so useful. An open Internet connection with T1 lines will call up a [...] bookmark faster than your CD drive can wake up. The alphabetical layout of the book makes it a quicker and more useful reference than the CD.

Layout style standards or advice is not given in this manual. No suggestions are made for banners, headlines, gutters, mastheads, graphics, photographs or hyperlinks. This sticky area of personal opinion and taste remains a wrestling mat issue for you to tackle on your own.

If you are writing a technical oriented project, this is the stylebook. As opposed to the Chicago Manual and the AP Stylebook, this compendium address the technical grammar issue your will encounter.

Unlike other "new economy" stylebooks, this is traditional. You can submit projects using it to crusty, old traditional editors without fear of embarrassing yourself. The word "Data" remains plural; the preposition "over" refers to spatial relationships, "more than" numeric relationships. It is easy to use and comes with a CD-ROM, which aids accessibility.

When I was first introduced to this book, I must admit I thought, "Why bother?" Having bought it and used it extensively, I now think, "Don't do without."

Let me say straight up that I'm not a Microsoft promoter. So this book really had to work hard to make me a fan.

I write and edit technical documentation and have found this book a great reference for terms of reference. I may not agree with some of the references, but the definitions are written clearly and concisely. Many provide examples for unmistakeable clarity.

One of the best resources available for technical publications.

I bought the first version years ago, and this latest version as soon as it came out. Nearly every technical writing friend who has seen it on my desk immediately went out and bought a copy. I probably use it two to three times a week to look something up or to settle an argument.

Every technical writer in the software industry needs this book. It deals with technical publication writing standards that don't only apply to Microsoft. As far as I know it's the only book of its kind--because of this, it will likely become THE standard for technical writing styles. The entries are up-to-date. They contain common usage, spelling, valuable information, examples, and so forth. I use it all the time.