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: Things not to put after a full stop. From:Tom Murrell <trmurrell -at- yahoo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 23 Jul 2002 05:53:20 -0700 (PDT)
--- Dick Margulis <margulis -at- mail -dot- fiam -dot- net> wrote:
>
> At the high level, though, let me put it this way. There is such a thing as a
> well-formed utterance, that is, one that is recognized by native speakers as being
> part of the language. And there is such a thing as an ill-formed utterance, one
> that is not recognized as being part of the language.
I agree with the notion that readers can recognize the "well-formed utterance" and
distinguish it from the "ill-formed utterance." I'm not sure I would limit the
recognition to native speakers alone, however. (But then I suspect you didn't intend
to rule out the competent reader form whom English is not the primary language or
the first language learned.
> So let's not throw out the baby with the bathwater. Otherwise, we'll all be out of
> a job and the developers and marketers will write the doc.
Gee, I am troubled by the notion that we sustain our jobs by the development of a
set of rules so arcane that only we can properly execute them, thereby insuring that
we have employment. I don't know how much of my job is dependent on knowing and
following the rules and how much of it is dependent on how effectively I help people
communicate information. I know that if I can more effectively communicate by
breaking the rules, I do so. But I also know that technical writing is not about
having arguments with SMEs and readers over things like comma use or whether there
should or should not be a semi-colon here or there or whether a sentence can be
started with a conjunction.
=====
Tom Murrell mailto:tmurrell -at- columbus -dot- rr -dot- com
Personal Web Page - http://home.columbus.rr.com/murrell/index.html Last Updated 07/19/02
--The opinions expressed in this email are mine...at least I think they're mine...I'm almost positive.--
__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
Buy RoboHelp Deluxe starting at only $798: you'll get RoboDemo, the hot new
software demonstration tool that's taking the Help authoring world by storm,
together with RoboHelp Office. Learn more at http://www.ehelp.com/techwr-l
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.