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: Alternative to typo? From:Peter Neilson <neilson -at- windstream -dot- net> To:John Posada <jposada99 -at- gmail -dot- com> Date:Fri, 27 Mar 2009 10:05:59 -0400
Actually, in spite of Geoff Hart's criticism of the engineering
involved, there are circumstances where erroneous commands cannot be
trapped beforehand. Both the super user on a Unix system and the guy
with a loaded six-shooter in his hip holster are ready and able to shoot
themselves in the foot.
The term "typo" is actually very bad, because it refers to an error in
print. Typos are the errors you see when you get the first box of books
back from the printing company, proudly take one out, open it to any
page, and utter expletives. They were originally caused by typographers,
the fellows who stood in front of a California case* of hand-set type,
putting individual letters backwards into a composing stick. Later they
were succeeded by Lino operators who etoain shrdlu had their own
problems shrdlu shrdlu shrdlu. Typographers traditionally blamed typos
* There was an UPPER CASE and a lower case. Yes. that's where the terms
John's version is good. Use it. Then tell the poor creep where to kick
the unit to restore its soul.
John Posada wrote:
> "Entering an error in this command may render the unit unresponsive."
> On Fri, Mar 27, 2009 at 9:12 AM, Geoff Hart <ghart -at- videotron -dot- ca> wrote:
>> Joel wondered: <<For some reason I am having trouble coming up with an
>> alternative to "typo." I have a sentence that says: "A typo in this
>> command may render the unit unresponsive." Should I change it to, "a
>> typographical error"? That sounds stuffy. "A mistake in typing..."?
>> Something else?>>
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-