http://tc.eserver.org/publisher/ISTC A listing of works published by ISTC in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/ISTC http://tc.eserver.org/30788.html http://tc.eserver.org/30788.html ASD-STE100 Simplified Technical English (formerly AECMA Simplified English) is a specification for writing aircraft documentation. The principles can be applied to all industry sectors. ASD-STE100 provides a set of writing rules and a dictionary of words and their meanings. It has a limited number of words; a limited number of clearly defined meanings for each word; a limited number of parts of speech for each word; a set of rules for writing text. This article outlines the standard, and shows how it helps to prevent ambiguity in text. http://tc.eserver.org/23221.html http://tc.eserver.org/23221.html Funny thing, documentation. Ought to be easy enough, surely? So why the disappointing results? What IS the elusive spark which distinguishes the professional author from others who put their hand to the pen (keyboard)? http://tc.eserver.org/23224.html http://tc.eserver.org/23224.html A description of the profession of scientific and technical communication. http://tc.eserver.org/23222.html http://tc.eserver.org/23222.html What does a technical writer do? A technical writer prepares information that helps users. http://tc.eserver.org/23223.html http://tc.eserver.org/23223.html Why use technical communicators? Why join the ISTC? How to become a technical communicator? This presentation should take approximately 40 minutes to complete and is designed for an audience who are not aware of the existence of the profession. http://tc.eserver.org/23219.html http://tc.eserver.org/23219.html Humorous examples of accidental (and humorous) errors in technical descriptions. Most of the gems on the following pages were, thankfully, picked up at the editing stage. One or two slipped through into printed books; some didnÕt even get as far as first draft stage. We have wondered for a long time about the mentality of the people who write this sort of thing; now you, too, can sit at your desk and try to figure out what these technical authors (yes, they actually get paid for this!) and engineers are on, where they got it from and whether they will give you some. http://tc.eserver.org/11761.html http://tc.eserver.org/11761.html A list of problems allegedly noted by U. S. Air Force pilots and left for maintenance crews to fix before the next flight, plus the replies from the maintenance crews. http://tc.eserver.org/11760.html http://tc.eserver.org/11760.html Questionable warnings and instructions from all over the world. http://tc.eserver.org/11763.html http://tc.eserver.org/11763.html Quotations of translated material from all over the world. http://tc.eserver.org/10129.html http://tc.eserver.org/10129.html A UK organization (member of Intecom) that allows members to exchange views and information with other technical communicators. Offers book reviews on various subjects (e.g. editing, writing, indexing, web design, user interface design, and programming and mark-up languages). It also offers information on training and education for technical communicators.