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: The Burden of Screen Captures From:LDurway -at- pav -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 22 Nov 2002 16:50:21 -0600
> 1. Is there an easier way to do this, one that I am
> overlooking? I can't
> imagine that Adobe or Microsoft or any other large software
> company have 10
> persons sitting in a room all day doing screen captures for
> their manuals,
> in 25 different languages?
I have two suggestions.
One=============
If you're a FrameMaker user, I assume you're using import-by-reference
rather than copy-into-document? It's easier to replace/update graphics then
because you don't have to mess with Frame at all (assuming the size of the
screen doesn't change). You just replace the file, and Frame picks it up
the next time you open the document.
Two============= (This works only if you import-by-reference)
Look into getting capture/replay software that will run your software and
grab the screen captures while you're at home in your sauna quaffing
aquavit. I asked our tester here, and she gave me a list. She's not
impressed by any of them, btw.
I don't know which, if any, are appropriate for your needs. Some may be
language specific (motif, java, etc.)
To convince your manager that capture/replay software is a good investment,
make an argument that emphasizes:
-faster turnaround (time savings through automation)
-better quality (reliable & consistent performance of repetitious tasks)
-more consistent scheduling & pacing (if the script takes 1 hr. to run, you
know that no matter how many screens have changed, it'll take you no more
than 1 hr. to update the docs)
The odds are that your developers or testing department already have
capture/replay software that they use for testing the product. You might
want to talk to them first. They may be able to help you set up the
scripts. As for automated screen capture software, I'm not sure. The last
one I used was called ImageMagick (UNIX only?).
Best wishes,
Lindsey
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Order RoboHelp X3 in November and receive $100 mail in rebate, FREE WebHelp
Merge Module and the new RoboPDF - add powerful PDF output functionality
to RoboHelp X3. Order online today at http://www.ehelp.com/techwr-l
Check out SnagIt - The Screen Capture Standard!
Download a free 30-day trial from http://www.techsmith.com/rdr/txt/twr
Find out what all the other tech writers, including Dan, already know!
---
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.
