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.
>From the Creating Single Source Images topic in Flare's help:
"The typical DPI setting for images displayed in an Internet browser
is usually somewhere between 72 and 96. The DPI is automatically set
for online output when you capture the image, depending on the
computer that you are using. However, the DPI setting for printed
output often needs to be higher (say, 300 DPI). "
Actually, a dpi somewhere around 72 to 96 (comparable to the
resolution of computer displays) is the setting that will make screen
captures easily readable in printed output and 100% zoom in Acrobat.
The same 72-96 dpi is also good for browsers since you're viewing the
screen shot on a screen of roughly that resolution.
It sounds like Flare is inappropriately resizing images for PDF.
On Thu, Sep 19, 2013 at 10:57 AM, Shawn C <shawn -at- convergent -dot- io> wrote:
> Hello all,
>
> My first attempt at a new thread. Please be kind.
>
> I already posted a similar message to the MadCap forum so the purpose of
> this message is to explore this as a broader issue and hopefully discover
> some best practices.
>
> I am a brand-new (1 month) user of MadCap Flare, but a long time Adobe
> FrameMaker and Microsoft Word technical writer. Recently, I have
> encountered major issues with images when publishing a Flare project to a
> PDF file. The problem is that, at less than 100% zoom level, images are
> oddly pixelated (badly rendered).To add some clarity, my images are
> generally inserted at slightly greater than 300 DPI. So, I am using
> slightly higher than normal resolution... maintaining a balance of file
> size vs image quality considerations.
>
> I don't recall running into such image problems under Word or FrameMaker so
> my finger is pointing is pointing at Flare.
>
> After some experimentation, I found that by integrating GhostScript with
> Flare, I can use .eps [vector] images, the results are images that render
> perfect at all zoom levels, inside a PDF.
>
> Part 1 of 2 solved! That is because the .eps format will obviously only
> work on vector friendly images, like our corporate logo. Now, what do I do
> about screen captures? Screen captures are a very important part of my
> documentation. Any thoughts?
>
>
> Thank you,
> --
> Shawn Connelly
> technical writer
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
>
> Learn more: http://bit.ly/ZeOZeQ
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as robert -at- lauriston -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
>
> Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
