Graphics

SLBwriter wrote: Why do images become bitmapped in FrameMaker? (I know...low resolution and the wrong type of file used...) However, my SME insists of using  PNG images at 96 dpi. Our standard is: 96 dpi for small images; 150 dpi for medium images; and 300 dpi for large images (500 x 700 pixels max.) I've tried to explain this to the SME with no luck. He's making Snagit capture at 96 dpi. And I've been told to "ONLY USE HIS IMAGES THE WAY THEY ARE."  I have some success with importing an image into a "frame" within a Anchored frame so that I can have a precise size for the image. But if I have to reinsert the image, size the image in FM, or just look at it "funny," it becomes bitmapped. Then I get the "evil eye" from the power-that-be for making bad images. Then I have to get a fresh image from my backup folder. What's a poor tech writer to do?!  Why can't Adobe make the use of images in FrameMaker more stable...easier...? Don't they know they are ruining my life?!  (I'm just kidding, hopefully!)

There's an easy fix for this. Get whomever is the highest-level arbiter to decide if the stuff's supposed to look its best, or if an arbitrary rule that makes it look bad is the ruling thing. It would help to show examples of what's possible the right way, and what you get the destined-to-degrade-and-fail way. Then, let that person decide.

You might get some advice by posting your question to the techwriter peers on the techwr-l.com forum. There's not a sliver of a doubt that you're in a unique situation.

HTH

Regards,

Peter

_______________________

Peter Gold

KnowHow ProServices