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: Total Confusion; was, "RE: RoboHelp: Ready to Publish...how doI do that?"
Subject:Re: Total Confusion; was, "RE: RoboHelp: Ready to Publish...how doI do that?" From:Rick Stone <rstone75 -at- kc -dot- rr -dot- com> To:"Leonard C. Porrello" <Leonard -dot- Porrello -at- SoleraTec -dot- com> Date:Mon, 18 Jan 2010 16:13:43 -0600
Indeed Leonard and I were able to come to terms with the situation. And
I'm quite happy to report that it was just a simple misunderstanding and
that no duel ensued. After all, the pen may be mightier than the sword,
but when one begins lobbing nuclear warheads, well, it just ruins your
whole day. ;)
As an aside, I find it to be both amusing and a great testament to the
difficulty communication actually can be. I mean, after all, if we
sometimes have issues properly communicating amongst ourselves, the
great "communicators", it's quite a testament to the possible difficulty
of our chosen profession, no? ;)
Okay, onward ho! Anyone have suggestions for typing while little dogs
stand on your arm and insist on licking your hand as you try to type and
Cheers... Rick :)
Leonard C. Porrello wrote:
> A most interesting and amusing salutation, Mike. And as to your
> question, "did you not read the subject line?"; the answer is, "yes."
> I glad you troubled to write as you raise a very important point
> regarding style and tone. We differ in opinion as to whether Rick's
> message was "totally" appropriate. I would stop at saying that it was
> "somewhat" appropriate. As you know, the technical writer is concerned
> with nothing if not decorousness, and Rick's tone was indeed
> regrettable. And while I admire his (and, indeed, your) chivalrousness
> in coming to the aid of a befuddled fellow technical writer, and he and
> I have in fact sorted out the matter between ourselves without having
> had it come to a duel (a fact which you may have discerned had you read
> the entire thread before responding to it), I would nevertheless venture
> to say that the message itself was less than "totally" appropriate.
> Having said that, I would be remiss were I not to confess that I accept
> full responsibility for the fact that Rick was "totally confused."
> In conclusion, as evidenced by this most unfortunate misunderstanding
> and, in fact, in this very massage, the style and tone used when
> writing, as you well know, is as important to ones massage as the
> content one wishes to communicate.
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: 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-