TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Correct Wording for Examples From:Stephen Victor <svictor -at- HOUSTON -dot- GEOQUEST -dot- SLB -dot- COM> Date:Fri, 22 Nov 1996 16:10:25 -0600
Gillian McGarvey wrote:
> Is it correct that we generally shouldn't use abbreviations like "e.g."
> and "i.e." in order to avoid giving the user any extraneaous terms that
> cause the reader to process more info than they must already?
Some consider these abbreviations difficult for non-native speakers of
English to understand. They might also be a problem for translators, who
often are themselves not native speakers of English. Instead (so the
story goes), we should use their full English equivalents ("for example"
and "that is").
> And, if the answer to the above is yes, what is the correct punctuation
> for the following sentence? (pls ignore the yucky wording of the example)
> "Below admin.ini are the Group INI files which are named by the group,
> for example, staff.grp and library.grp."
This sentence should be punctuated as follows: "Below admin.ini are the
Group INI files, which are named by [delete "the"] group; for example,
staff.grp and library.grp."
Stephen P. Victor Phone: (713) 513-2552
Technical Writer, Software Training Fax: (713) 513-2019
Schlumberger GeoQuest svictor -at- houston -dot- geoquest -dot- slb -dot- com
5599 San Felipe, Suite 1700
Houston, Texas 77056 USA