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 vector stuff is perfectly clear. It's the screen-shot bitmaps that
are confusing. I don't understand what Flare is doing and can't make
sense of their online help.
For example, if you take e.g. a screen shot of a 450 x 300 dialog box
and place it in a page layout program at 300 dpi, it will be a 1.5" x
1" postage stamp and none of the text will be readable. If you place
it at 75 dpi, it will be 6" x 4" and easily legible.
Are you resizing the images (interpolating extra pixels) to blow them
up to 300 dpi?
On Thu, Sep 26, 2013 at 4:56 PM, Shawn C <shawn -at- convergent -dot- io> wrote:
> Hello Robert,
>
> The resolution was multi-part.
>
> Best Practices:
> - Use vector source files where possible (company logo, all my tech
> drawings)
> - All bitmaps should be a minimum of 300DPI (if possible)
>
> How to use them:
>
> Vector: I needed to install GhostScript for .eps and my MadBuild server
> needed Java installed to render .svg images (output from Visio).
> Bitmap: Just try to output the largest practical size possible.
>
> Finally, configure TARGET PDF image compression from "JPEG" to "Automatic"
>
> The reason why I was encountering problems was because of old habits. In
> the past, an image at 1:1 was good enough for acceptable PDF output. But
> Flare handles images a bit differently and 1:1 source images output poorly.
>
> Sorry, I've rushed through this reply. Feel free to ask me to clarify
> anything and I will tomorrow. My ride is here... leaving the office now. :-)
>
>
>
> On Thu, Sep 26, 2013 at 4:44 PM, Robert Lauriston <robert -at- lauriston -dot- com>wrote:
>
>> You resolved that issue? What was the fix?
>>
>> On Thu, Sep 19, 2013 at 2:45 PM, Shawn C <shawn -at- convergent -dot- io> wrote:
>> >>It sounds like Flare is inappropriately resizing images for PDF.
>> >
>> > Something is up in Flare. Like I previously mentioned, I never
>> encountered
>> > such a problem in either FrameMaker or Word.
>> >
>> > I need to work on content now, so I'll revisit this problem over the
>> > weekend.
>> >
>> > On Thu, Sep 19, 2013 at 12:31 PM, Robert Lauriston <robert -at- lauriston -dot- com
>> >wrote:
>> >
>> >> 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.
>> >>
>> >>
>> >>
>> http://webhelp.madcapsoftware.com/flare9/Default.htm#Images/Creating_Single_Source_Images.htm
>> >>
>> >> 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
>> >> >
>> >> >
>> >>
>> >>
>> > --
>> > Shawn Connelly
>> > technical writer
>> > <http://convergent.io> <shawn -at- convergent -dot- io>
>> >
>> >
>> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> > 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
>>
>
>
>
> --
> Shawn Connelly
> technical writer
>
> <shawn -at- convergent -dot- io>
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 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.