| |||||||||
|
1. #21216 The ABCs of Writing a Technical Glossary This article identifies and explains format rules, style rules, and lexicographic conventions that have been shown to improve clarity and precision in a technical glossary. Rationale for the rules of language, presentation, and style are examined. The need to allow flexibility in following the rules is discussed in terms of strengthening the technical merit and vitality of the glossary. This article also describes the computer-display techniques and file-management system used in committee to develop U.S. Federal Standard 1037C, Glossary of telecommunication terms, and to display the results both in the meeting room and on the Internet between meetings. Gray, Evie, William Ingram and Dennis Bodson. Technical Communication Online (1998). Articles>Editing>Technical Editing>Glossary 2. #22128 'It's all in the manual.' How many times have you heard that - or said it in frustration? After all, when you are the person who wrote the manual, you know that all the answers are there. But time and again readers can't find what they need to know, or don't understand the material. Before you blame the reader, look again at how you've presented the material. Hollis Weber, Jean. Technical Editors Eyrie (1989). Articles>Editing>Technical Writing 3. #23799 Ask the Indexer: Get Answers to your Indexing Questions from Experienced Technical Indexers After brief introductions by 4 panelists who are all members of the Indexing SIG (and experienced indexers and technical writers), we plan to discuss Frequently Asked Questions (FAQs) about indexing, and allow plenty of time for questions. Bonura, Larry S., Dick Evans, Joan K. Griffitts and Peg Mauer. STC Proceedings (1999). Articles>Indexing>Technical Editing>FAQ 4. #14383 Becoming a Journal Peer Reviewer This session will help participants understand the process for reviewing manuscripts submitted to Technical Communication. It covers the types of articles the journal publishes, review procedures and criteria, and approaches to writing constructive evaluations. Hayhoe, George F. STC Proceedings (1998). Presentations>Editing>Technical Editing 5. #25310 Controlled Languages in Industry A Controlled Language is a form of language with special restrictions on grammar, style, and vocabulary usage. Typically, the restrictions are placed on technical documents, including instructions, procedures, descriptions, reports, and cautions. One might consider formal written English to be the ultimate Controlled Language: a form of English with restricted word and grammar usages, but a standard too broad and too variable for use in highly technical domains. Whereas formal written English applies to society as a whole, CLs apply to the specialized sublanguages of particular domains. Wojcik, Richard H. and James E. Hoard. Oregon Health and Science University (2005). Articles>Language>Technical Editing>Controlled Vocabulary 6. #21317 Coping with Wordslaughter and the "Good Enough" Syndrome Connatser provides advice for technical editors who aren't granted enough time or money to perform extensive revisions on poorly written documents. Connatser, Bradford R. Intercom (2004). Articles>Editing>Technical Editing 7. #19816 Copy Editors and Technical Editors: We are Family The authors of this paper have the unusual background of having worked in both the newspaper (copy editors) and business (technical editors) fields, which are not as diverse as people might think. Huth, Elizabeth Ann and Kevin J. Schmidt. STC Proceedings (1995). Careers>Editing>Technical Editing 8. #28826 Core Principles of Information Architecture Technical editing is like information architecture. As technical editors, we complete development edits and usability edits to ensure organization, labeling, navigation and search meet the users' needs. As information architects, we are involved with "the design of organization, labeling, navigation, and searching systems to help people find and manage information more successfully." Corbin Nichols, Michelle. STC Proceedings (2007). Presentations>Information Design>Technical Editing 9. #13722 Courses for Technical Editors in Australia I don't know of any tertiary-level courses in Australia specifically for technical editors, although there are several programs for general editors or journalists. I'll add information to this page as I find it. Technical Editors Eyrie. Academic>Courses>Technical Editing>Australia 10. #20549 Like many of you, I come from a training background. Like many of you, we’re experts in group facilitation, engaging our learners, and creating instructionally sound materials. Yet, many trainers are not graphic artists nor do we have a score of graphic artists helping us create our training presentations. As a result, our training presentations often may not adequately represent the professionalism and quality that we’ve built into our training. Traut, Terence R. Presenters University (2003). Design>Graphic Design>Image Editing>Technical Illustration 11. #22125 Tables should allow readers to easily and accurately: see what subject matter and variables are being described; find out absolute values; observe relationships between variables. When you edit a table, it is useful to assess just how well it achieves these ends. Readers will feel confident with your table if they can quickly navigate around and absorb the data. Hollis Weber, Jean. Technical Editors Eyrie (1999). Articles>Editing>Technical Editing 12. #26119 Collection of principles that can also form a process for editing web content to make it usable. Jarrett, Caroline. Editing That Works (2005). Resources>Editing>Technical Editing>Usability 13. #21411 Editing Your Own Documentation Technical writers sometimes fall into the trap of thinking that the user is stupid. I have often heard technical writers say things like 'well, if the user can't figure that out, maybe he’s in the wrong job!' Docsymmetry (2003). Articles>Documentation>Editing>Technical Writing 14. #30361 Here are some tips that helped me edit my own writing. Leigh, Heather. Crazy for Words (2007). Articles>Editing>Writing>Technical Writing 15. #27092 Electronic Reporting of ANSYS Results This documents several ways to get ANSYS plots into your reports without getting out of your chair. Bright Path Solutions (2005). Design>Graphic Design>Technical Editing 16. #29647 Experiencing Technical Writing as Textual Coordination This paper describes a recent study of how of four technical writers managed the many artifacts (existing texts and information technologies for producing and manipulating text) that mediated their writing process. The author describes the study and characterizes several recurrent patterns of mediation, including textual reuse, remediation of information, and the staging of texts and software programs. The author describes the value of a repertoire of information technologies to technical writing and argues that technological skill should be considered a core competency of the field. Slattery, Shaun. STC Proceedings (2005). Articles>Writing>Technical Editing>Technical Writing 17. #22691 Don't you think that it is a tragedy that 95 percent of the people who desire to be technical writers have a poor command over the language? I am sure all of us make a mistake or two, once in a while. But to make it in every sentence and paragraph shows utter disrespect for readers. Kamath, Gurudutt R. IT People (2003). Articles>Editing>Grammar>Technical Writing 18. #30818 Hockey Sticks and User Assistance: Writing in Times of Resource Constraints If you have all the resources you need, do the very best job you can in all respects. But if your resources are tight, ask yourself whether you are writing the essential stuff at a level of quality users will notice. Also, ask whether the value of the documentation you are producing aligns with the economic pressures on your company. Hughes, Michael A. UXmatters (2008). Articles>Writing>Technical Editing 19. #19673 Editing involves more than just formatting and inserting page numbers. You need to ask, 'How can I improve the communication?' Bush, Donald W. Intercom (2003). Articles>Editing>Writing>Technical Writing 20. #21380 If a document contains the information that a reader needs, but if the reader cannot find that information, then the document is useless. Worse than useless, it’s a hindrance. If I know that some information is not available, I won’t waste my time looking for it. However, if I think the information is available, and if I can’t find it after a period of fruitless searching, all I will have achieved is frustration. TechScribe (2004). Articles>Indexing>Technical Editing 21. #26025 Indexing Technical Documents: An Interview with Lori Lathrop Indexes are as important to your documentation as your documentation is to the product. Just as it would be difficult, if not impossible, for people to use your product without any documentation, it is equally difficult for people to use documentation without a good index. Vega, Barbara. Writing World (2001). Articles>Indexing>Technical Editing 22. #23453 Knowledge Management - Challenge for Technical Editors Knowledge management - is it a challenge for technical editors? Shouldn't knowledge management be more than just taken for granted in technical editing? And isn't the technical editor also the knowledge manager, per se? Sturz, Wolfgang. TC-FORUM (2000). Articles>Knowledge Management>Technical Editing 23. #22690 Learning the Fine Art of Reviewing If you asked me what the most painful part of being a technical writer is, my answer would be: 'Getting reviews on time. Getting good feedback and inputs on your work.' For me technical writing has been very pleasurable because I hardly got any review comments. My morale has therefore been very high. Project managers, developers and others are so busy trying to come up with good software (read trying to fix all the goof-ups and bugs!) that they usually tend to give documentation lesser importance. User manuals, who reads them anyway? We do not have time for it! Kamath, Gurudutt R. IT People (2003). Articles>Editing>Collaboration>Technical Writing 24. #21305 We technician editors need not worry about declining employment if we can show companies the value of the technology of English. If we can demonstrate how editors can make turgid technical authors communicate better with words, sentences, paragraphs, and overall organization, we will be in demand for jobs that are more prestigious and careers that are infinitely more interesting -- because the need is so great. Bush, Donald W. STC Proceedings (1995). Articles>Editing>Technical Editing 25. #24352 Mystery Fiction and the Technical Communicator: The Editor's Role Technical editors can learn much from editors of mystery fiction. Both orchestrate elaborate game-playing and structuring as they serve as the reader's advocate. Murphy, Avon J. STC Proceedings (1998). Articles>Editing>Technical Editing
| |||||||||
| |||||||||
Click here to learn how to embed the RSS feed of this category in your website.