Article View: adobe.framemaker
Article #1872Re: Can't generate PDF
From: Ian Hawkins
Date: Tue, 21 Oct 2008 04:48
Date: Tue, 21 Oct 2008 04:48
44 lines
2668 bytes
2668 bytes
The problem with fuzzy screen caps in PDF is usually more a function of monitor technology and Acrobat than FrameMaker. I'll see if I can explain. Suppose you have a screen cap that is 200 pixels wide, 100 pixels high. To get this to display properly on a monitor, you want each one of those pixels to correspond exactly to a physical pixel on the monitor. If they don't match, then Acrobat has to interpolate, which leads to loss of quality. So as you zoom in and out using Acrobat, you are changing the mapping between image pixels and monitor pixels. For any given image in a PDF, there is only one perfect Acrobat zoom level. You have control over the size of your image in the PDF, but you have no control over how users view it in Adobe Reader. The best you can do is try to lead your users to an optimal zoom level. This is imperfect at best. Try this: 1. Create an empty FrameMaker document 2. Import a single screen cap. Set the DPI to custom, 96 DPI. 3. Create a PDF. 4. Open in Acrobat, and view at 100% zoom (what Adobe calls "Actual size"). How does it look? If it is still fuzzy, open your Acrobat preferences (CTRL+k). Open Page Display, or Display Options, or something like that (it seems to move around in different version of Acrobat, and all I have in front of me is version 6). Somewhere, there should be a display resolution option. If you want a screen capture to be perfect in Adobe Reader or Acrobat, then you should import images at that resolution, then display the PDF at 100%. On Windows, the default system setting is 96 DPI, but users can change that. You have no way of controlling how your users have set up their systems, so you have no way to ensure that they can find the proper zoom level. HTML works differently. Images are supposed to display at 100%, where every pixel in the image corresponds to a single pixel in the display. HTH, Ian
Technical Details
Message-ID:
<CD3BAEE264405252D604984B42206468@in.webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!proxad.net!feeder1-2.proxad.net!feeder.erje.net!news4us.nl!webcrossingReferences:
<59b6c55b.-1@webcrossing.la2eafNXanI> <59b6c55b.7@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: fd315,d3b3df2bddc6fe0f X-Google-Attributes: gidfd315,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: Ian Hawkins <ihawkins@sundorne.com> Newsgroups: adobe.framemaker Subject: Re: Can't generate PDF Message-ID: <CD3BAEE264405252D604984B42206468@in.webcrossing.la2eafNXanI> Date: Mon, 20 Oct 2008 21:48:50 -0700 References: <59b6c55b.-1@webcrossing.la2eafNXanI> <59b6c55b.7@webcrossing.la2eafNXanI> Lines: 54 User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!proxad.net!feeder1-2.proxad.net!feeder.erje.net!news4us.nl!webcrossing