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.
Yesterday, I posted the message below but when it showed up on the list
it had been truncated and scrambled. Dunno why. If it looked OK to
you first time round, sorry to bother you with the repetition.
************
I received a private post on this subject with which I heartily agree:
While I like the idea of clearing labeling subject lines, I have
to shake my head at the concept that this group is going to
follow some set of preset labels.
Hey, Eric can't even get people to read instructions on how to
unsubscribe, set the digest, etc.; how on earth does anyone
propose to force them to use prescribed labels?
I hardly think people are going to be pulling up instructions,
trying to recall what is supposed to be used for job postings
(was that one $ or two?) or opinions (OPED? MHO? RIGHT?), at
the moment that inspiration strikes.
Let us simply ask that everyone LABEL their subject lines in
a way that appears to be intelligible. JMHO.
I posted the copyeditors list because I don't relish the idea of having
to remember two sets of labels. But the idea quoted above, that the
label not be from a prescribed list but simply be there and be intelligible,
is much better. What label should I have used for this post? Or would
we not need a label when just continuing discussion of a topic identified
in the subject line?