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.
>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 capture?
Noelle: a few troubleshooting questions for you:
1. What format are you saving your screen captures in? (bmp, eps, etc.)
2. Are you porting your screen captures cross-platform?
3. How are you putting your graphics in your docs?
a. Import by Reference
b. Copy into Document
4. Are you distorting your graphics in any way when you bring them in?
5. Are you using screen capture utilities, or the platform's
built-in screen capture ability?
Importing by reference keeps your file sizes smaller, and allows for
automatic updates on your screen captures.
If you are resizing your graphics, are you using the Scale command
(preferred), or grabbing the corners of the graphic and manually resizing?
(this is a really *baaaadddd* thing to do!)
We can continue this troubleshooting off the list if you'd like.
Carla Martinek (carlam -at- opentext -dot- com) | Visit the Open Text
Open Text USA, Inc. | WWW Search Engine
business intranet solutions | at http://www.opentext.com/ http://www.opentext.com | omw/xpowrsrch_c.html
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-