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.
Re: The Ancestral Territorial Imperatives of the Trumpeter Swan
Subject:Re: The Ancestral Territorial Imperatives of the Trumpeter Swan From:Ken Poshedly <poshedly -at- bellsouth -dot- net> To:David Neeley <dbneeley -at- gmail -dot- com>, TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 30 Mar 2010 10:41:53 -0700 (PDT)
Sorry for the goof-up -- I meant the "xxxx for Dummies" line of books.
-- Kenpo
________________________________
From: Ken Poshedly <poshedly -at- bellsouth -dot- net>
To: David Neeley <dbneeley -at- gmail -dot- com>; TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com>
Sent: Tue, March 30, 2010 1:38:28 PM
Subject: Re: The Ancestral Territorial Imperatives of the Trumpeter Swan
(stuff snipped)
The familiar "xxxx for Idiots" books now seen almost everywhere probably got their start on the coattails of the first real "idiot book" by the late Mr. Muir. Any VW nuts out there with VW stories to share write to me off-list.
-- Kenpo in Atlanta
________________________________
From: David Neeley <dbneeley -at- gmail -dot- com>
To: TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com>
Sent: Tue, March 30, 2010 10:36:52 AM
Subject: The Ancestral Territorial Imperatives of the Trumpeter Swan
Believe it or not, that was the title used instead of "Getting
Started" in the early 1980s manual for the Franlin Ace 100 computer,
and for its replacement the Ace 1000.
See excerpts and why they used it in reproductions at the Ironic Sans blog.
Which brings me to something of a lament that most manuals today seem
to lack personality, let alone humor.
I have long been a fancier of a very conversational style for user
manuals (within reason, of course)--avoiding the stuffy verbiage that
so often seems to stem from an over-reliance on a legal department.
There's something about users enjoying a manual that seems to me to
mean it may be more memorable, inviting a user into it--and, with
luck, cutting down on user frustration and tech support overhead at
the same time.
I can imagine that most docs managers today would have a heart attack
over the Franklin approach, though.
David
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as poshedly -at- bellsouth -dot- net -dot-
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
