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: Into the Frying Pan From:Ken Poshedly <poshedly -at- bellsouth -dot- net> To:Peter Neilson <neilson -at- windstream -dot- net>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>, Chris Morton <salt -dot- morton -at- gmail -dot- com> Date:Thu, 1 Oct 2015 14:22:35 +0000 (UTC)
Regarding producing a pdf file for review by the ignorant masses, open your file in Acrobat (we use Acrobat Professional), then under the "Comments" drop-down, simply left-click on "Enable for Commenting and Analysis in Adobe Reader" and re-save the file.
Those with Adobe Reader will then be able to use the "Commenting" tool that should be in the menu bar (top of the screen) for various comments, etc.
NO ACTUAL EDITING can be done by the reviewer.
At least this has been MY experience.
-- Ken in Atlanta
On Thursday, October 1, 2015 9:52 AM, Peter Neilson <neilson -at- windstream -dot- net> wrote:
On Thu, 01 Oct 2015 08:22:10 -0400, Chris Morton <salt -dot- morton -at- gmail -dot- com>Â
> Surprise! As of Tuesday afternoon, the state was up in arms that the plan
> had not already been finalized, submitted and approved.
>I was supposed to help guide them, collect inputs, and then magically
> assimilate all changes into a perfectly formatted, state-"presentation
> ready" doc by 2:30. The SME conference lasted until noon, and I'mÂ
> to "punch out" for an hour lunch (I cut my lunch break way short anyway).
> But I soldiered on ...
SSDD. Years ago my wife the quality engineer got a request that a test beÂ
run on some material. "That will take three days," she explained, "becauseÂ
the prep time for the setup is complicated, and the run time for theÂ
reaction is long."
"That won't do. We need the results this afternoon. Just give me theÂ
results, with your signature saying it all passes the test."
As you might guess, she eventually bowed out of quality engineeringÂ
entirely. The constant threats of being fired or of jail time for fraud,Â
or simply wanting to quit, take their toll.
Your new manager may have been hired to take the hit for the inevitableÂ
failure, sort of like this: "Yes, we know that we had a problem withÂ
quality, but we've solved it. We fired the quality engineer."
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com