 | | Style Guides 26-49 of 213 found. Page 2 of 9. |
#10715
A list of frequently used and sometimes misused words, their definitions and examples of their correct usage.
Author's Guide (2001). Reference>Style Guides
#10711
Commonly Used and Misused Punctuation Marks
Defines the functions of several punctuation marks and provides examples of their correct usage.
LR Communication Systems (1999). Reference>Style Guides>Grammar
#20095
Communicating in Spite of TLAs (Three-Letter Acronyms) 
The unchecked use of acronyms and initialisms in technical writing presents a huge obstacle to clarity and readability. Although technical communicators are certainly more aware of this problem than are the engineers, scientists, and managers with whom they work, they need concrete guidelines and at least a small degree of self-righteousness on this subject to help them cope with the onslaught. That acronyms frustrate communication is well-founded in linguistic theory and common sense. Suggestions for mitigating their effect include issues of audience, term selectivity, frequency and occasion of use, and aesthetics.
Miller, Diane F. STC Proceedings (1995). Articles>Writing>Style Guides
#29056
Committees within international standards organizations write standards. Prior to approval, these standards must pass through several reviews for technical accuracy and stylistic appropriateness. The style considerations are based on documents published by both the umbrella organization (International Organization for Standarization, or ISO) and the various committees and subcommittees within it. Because authors and editors who use these documents frequently do not have English as a first language, the documents must explain unambiguously just how committees should prepare their documents. This study looks at a sample of those instructional documents using Restricted and Elaborated Code and metadiscourse analysis to determine how easily users can read and understand the material. The findings suggest that the documents do not send a clear message to authors and editors and can be stylistically hard to understand. Consequently, the approved standards themselves are hard to read and interpret.
Warren, Thomas L. Journal of Technical Writing and Communication (2001). Articles>Editing>Style Guides>Standards
#23901
Provides alternatives to overstated, pompous words; wordy, bureaucratic phrases; and verbose, sometimes amusing redundant phrases.
#25797
Confusing Words is a collection of words that are troublesome to readers and writers. Words are grouped according to the way they are most often confused or misused.
#10780
This presentation introduces your students to the rules of comma usage, including placement in compound sentences, after introductory elements, with dependent phrases and clauses, around non-essential elements, in a series, and with adjectives. This presentation also covers methods for avoiding a common comma error--the comma splice. This presentation is ideal for the beginning of a composition course, the assignment of a writing project, or as a refresher presentation for grammar usage.
Liethen, Jennifer Kunka. Purdue University. Presentations>Slideshows>Style Guides>Grammar
#14335
As a writer, you need to know some strategies for developing the content for a writing project: what topics and subtopics to include, what to write about, how to think of material to cover concerning a topic.
McMurrey, David A. Illuminati Online (2001). Academic>Course Materials>Style Guides
#26138
Corporate Pages 2002-2004 (Part 2)
When training web authors, I prefer to use good examples of their kind, so these must have been either typical or among the best I could find at the time. However, they certainly did not contain content to skite about.
McAlpine, Rachel. Quality Web Content (2005). Design>Web Design>Style Guides
#25242
Creating, Implementing, and Maintaining Corporate Style Guides in an Age of Technology 
This article details a step-by-step process for creating, implementing, and maintaining a corporate style guide to ensure consistency in organizational communication. Through literature research, analysis of sample style guides, and practitioner interviews, this article provides recommendations for gaining management support, building a process to develop a style guide, determining content, encouraging employee buy-in, and maintaining a corporate style guide.
Bright, Mark R. Technical Communication Online (2005). Articles>Editing>Style Guides>Collaboration
#20433
Indenting the first line of every paragraph is a habit most of us acquired in grammar school. However, for those daring souls who have always insisted on coloring outside the lines, it’s time to consider using a different style paragraph indent. There are more options than you might have realized!
Strizver, Ilene. Upper and lowercase Magazine (2001). Design>Typography>Style Guides>Grammar
#23466
The Current Demand for Style Guides
During my research for a book project, I have found style guides in a wide variety of forms. Some are only a couple of pages. Others consist of hundreds of pages, delivered in ring binders. Some companies produce well-printed and bound books (for example, Microsoft and Sun). A lot of style guides, differing in quality and size, are in the Internet. Most of them cover the design of web pages; only a few deal with document design in general. From one company I received a multimedia CD containing their style guide. It is a well-designed piece of software, presenting graphic arts, sound and video.
Baumert, Andreas. TC-FORUM (1998). Articles>Style Guides
#24033
Several years ago, four new prefixes, for representing very large and very small measurements, were introduced into the International System of Units (Système International d'Unités, or SI): yotta, zetta, zepto and yocto.
Ivey, Keith C. Editorial Eye, The (1996). Articles>Style Guides>Standards>Scientific Communication
#10712
Lists common phrases that make wordy documents and makes suggestions for replacing them.
Author's Guide (2000). Reference>Style Guides
#18186
Design Guidelines for Written Assignments
This paper discusses design guidelines educators can use to format their assignment instructions. The purpose of formatting is to avoid students' misinterpretation of the assignment and to receive more readable papers. Topics covered are design awareness and formatting tips on using headings, chunking information, and using special features.
Dyrud, Marilyn A. University of Pittsburgh. Articles>Education>Style Guides
#18156
For this project, you'll create a style guide for at least two markedly different technical publications. Your style guide will be used by technical writers on your documentation team to get these publications in conformance with each other, as well as other publication.
Rogers, Will. Illuminati Online (2002). Academic>Course Materials>Style Guides
#30134
Designing Automated Custom Templates as Part of A Global Corporation's Style Guide
When CH2M HILL staff ignored the Times 12 standard for document production and began inventing their own formats, they often bypassed the company's Publications groups, resulting in client bewilderment and anger. We will orient the audience to how creative thinking and innovative programming made it easy for staff to produce consistently attractive and effectively formatted documents. We also will demonstrate the final Toolset version and supply information about how you can apply the benefits of a Toolset product in your company's environment.
Sippel, Martha K., Brock McFarlane and Deborah Gillespie. STC Proceedings (1998). Articles>Document Design>Style Guides
#22838
Developing a Company Style Guide
Every company that produces external publications--whether brochures, research papers, or reference manuals-benefit from a company style guide. This paper discusses the advantages of a style guide, why a company-specific style guide is preferred, how to develop a style guide, and what a style guide should (and should not) include.
Gelb, Janice and Jefferey J. Gardiner. STC Proceedings (1997). Articles>Style Guides>Editing
#29642
Developing a Corporate Style Guide
Developing corporate style guides helps documentation departments or any other group apply the same standards when writing documents for publication or presentation. Three types of style guides exist: static, dynamic, and multi-level. The information that goes into a style guide depends upon corporate and department guidelines. Publishing, promoting, and maintaining style guides are the responsibility of the responsible department. In many corporations this may be the technical documentation department, while for others it may be the corporate marketing or internal communications departments.
Damrau, Jackie. STC Proceedings (2005). Articles>Style Guides>Business Communication
#14140
Developing a Departmental Style Guide
As a technical writer, you may be asked to develop a style guide for the hardcopy and online documents you produce. Sounds easy enough. After all, commercial style guides and, potentially, examples shared by your colleagues should provide enough information to get you started. In researching your task, though, you may find a variety of definitions and explanations of what a style guide is and why companies use them. What's more, you many find that style guides don't seem to have consistencies among them that can help guide you in developing one.
Weber, Jean Hollis. TECHWR-L (1998). Articles>Style Guides>Workflow
#18279
Developing a Style Guide in the Real World
Style guides present a series of rules for standardizing writing. Style guide developers run the risk of concentrating too much on these rules, and too little on other factors that may ultimately affect the quality of the documents that are governed by the style guide. I would like to consider some of these other factors in this paper. I’ve drawn this discussion from Battelle’s efforts developing style guides in various industries. Another reason to involve your clients in the development process is to help ensure that the style guide includes the information they will need. For example, we included tips on using Microsoft Word in a style guide that would be used by writers working in Word. Don’t be afraid to be creative when deciding what to include in your style guide; if it gives writers a reason to look something up in the style guide,
Wieringa, Douglas. STC Proceedings (1996). Presentations>Documentation>Style Guides
#20133
Developing and Implementing Project Style Guides
Style guides can be very effective tools for achieving uniformity in documentation. Their use can enhance the appearance, readability, and tone of a document. In this progression session, I would like to discuss why style guides are needed, what should be included in them, and how to create a style guide appropriate for your project. I invite participants to bring style guides with them for critique and discussion.
Marks, Sandra R. STC Proceedings (1996). Articles>Style Guides>Editing
#20954
The buried treasures of typography: comprising the Style Guide of the Type Club of Toronto, with illustrations, and an Expert Font Guide.
Shinn, Nick. ShinnType (2001). Design>Typography>Style Guides
#10322
Disciplinary Style Manuals as Reliable Guides to Scientific Discourse Norms
Style manuals sponsored by professional associations in various scientific disciplines have received virtually no scholarly attention. These manuals, however, specify many disciplinary discourse norms that writers need to follow in publishing scientific research. Consequently, these manuals provide an important and reliable source of information about how communities of working scientists conceptualize, construct, and publish their scientific texts. The disciplinary norms that these style manuals promulgate derive both from general scientific research practices and from the practical demands of scientific publishing. Because of their unique normative nature and their connection with scientific practice, disciplinary style manuals should be categorized separately from other types of scientific style manual, and the material they contain can reliably be used in technical writing and editing.
Hagge, John. Technical Communication Online (1997). Articles>Scientific Communication>Style Guides
#23401
Do Not Forget Bibliographical Data in Technical Documentation!
Information products, e.g. manuals, drawings etc, must, besides the technical message, contain certain formal data, which too often is left out. Proper formal data contributes to good order and favours the producer as well as the user of information products.
Rullgård, Åke. TC-FORUM (1999). Articles>Documentation>Style Guides
| Copyright © 2001-08 by the EServer. All rights reserved. | Add a Work | Site Preferences | Discussion Forum | Habitués |
