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.
At 08:00 AM 7/18/96 HST, David Jones/KSBEISD wrote:
>>I am one of two tech writers working on software documentation manuals for a
>small company. Our dilemma has been quality screen capture. We have tried
>several methods. Our software is cross platform, so we are able to capture
>using workstations, PC's or MAC's. The captures are pretty good, but when we
>bring them into Framemaker, they get distorted, fuzzy and the text looks
>terrible (stairstepped). What are others out there using to get quality screen
Pay no attention to the way the screenshots look on-screen (unless, of
course, you're going online with the book). I've had good results using
just alt+print screen and saving the screenshot as a bitmap. I suspect
the problem lies in your import process. Frame suggests you use the number
of dots per inch setting to resize a bitmap and that the selected number
of dots per inch be evenly divisible into the number of dots per inch
print resolution. For example, if you're printing at 600dpi, import the
bitmap at 100, 150, 200, or 300 dpi (which gives you a choice of several
sizes that should all print out relatively well), but don't use 72 or
125 dpi because you cant divide 600 by these numbers and get a whole
sgallagher -at- expersoft -dot- com
-- The _Guide_ is definitive.
Reality is frequently inaccurate.
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-