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.
Etiquette for changing the subject line (was Re: TWs and Core Competencies (long))
Subject:Etiquette for changing the subject line (was Re: TWs and Core Competencies (long)) From:doc -at- edwordsmith -dot- com To:"jobs @ ProSpring" <jobs -at- prospring -dot- net> Date:Wed, 26 Dec 2007 10:05:31 -0800
On Sun, 23 Dec 2007 16:28:24 -0600, in bit.listserv.techwr-l you
>>> A similar situation exists with BA; TWs seem to be claiming BA skills to
>augment whatever other skills they list. That is ludicrous. A BA is
>primarily a position interfacing with upper management, secondarily with IT
>chiefs, and almost never with the lowly developers and documentation
>producers. The skill sets are totally different, yet many TWs seem to
>include BA in their skill list as a matter of course.
>Sorry, I had to change the Subject as the original email just had "RE:
>TECHWR-L Digest, Vol 26, Issue 21" as the subject.
Geez, great instincts, jobs! The re-focused subject line is
appreciated, and apology accepted. Now allow me to reciprocate with a
request for further deference, which you should feel free to dismiss.
I'm sending this to the list instead of privately because, in the age
of webmail, a lot of list subscribers may not know what threaded email
is. Maybe someone will appreciate the following tip.
When you change the subject line, you can better accomodate those of
us who use threaded mail readers by Replying to the original message,
and then editing the subject line, rather than starting a new thread
with a new subject.
If you do this for me, then my email program can detect your message
as a part of the converation begun by the original poster, and group
it accordingly as a follow-up to the original post.
If you don't do this, I get two top level posts sorted only by their
timestamps. Even if you create a new thread and give it the exact
same subject line as the original, they won't get threaded by my
reader, they'll be sorted as if they were unrelated.
I hope that mentioning these things won't aggravate those techwhirlers
who know about threaded mail readers but do not bother to stick their
responses into the original threads. I expect they have their reasons
for not doing so.
Thanks for your consideration, and for re-engineering bad subject
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-