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 "Creating Single-Source Images" in Flare's online help:
"Let's say you create a Flare project and you are using Capture to
produce images for it. You want to generate two different outputs from
that Flare project. Let's say the first output is an online Help
system to be placed on a website, and the other output is a PDF
document, which you will send to a printer. Right away, you have a
dilemma when it comes to the DPI (dots per inch) setting for the
images in your project. 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). Therefore,
when you edit the image in Capture, you use the Format tab in the
Image Properties dialog to specify the image settings for the online
output (you may elect not to change any of the default settings). For
print-based output, you use the Flare Print Format tab to specify the
image settings; in the DPI field, you may want to select 300. In
Flare, you insert the Capture image. When you generate output for the
website (e.g., WebHelp), Flare displays the image in the DPI used when
you captured the image (e.g., 96 DPI). When you generate the PDF
output from the project, Flare displays the same image in 300 DPI. "
This is nonsense. The DPI of screen shots in PDFs should usually be
similar to the PPI of a computer screen, which is typically 72 to 96.
If you set it to 300 DPI for PDF, the images would be tiny and you'd
have to zoom in to 3-400% to read the text in the screen shot.
On Mon, Sep 30, 2013 at 2:42 PM, Shawn C <shawn -at- convergent -dot- io> wrote:
> Which incomprehensible passage?
>
> On Mon, Sep 30, 2013 at 2:26 PM, Robert Lauriston <robert -at- lauriston -dot- com>wrote:
>
>> Screen shots are bitmaps. If getting screen shots in PNG format to
>> look good in both HTML and PDF output isn't extremely easy (that is,
>> if you have to do any kind of resizing or conversion), Flare has new
>> bugs or design flaws since 7.1.
>>
>> Which, given the incomprehensible passage on the matter in their user
>> guide, would not surprise me.
>>
>> On Mon, Sep 30, 2013 at 1:56 PM, Shawn C <shawn -at- convergent -dot- io> wrote:
>> > I have MadCap Capture but I haven't learned how to use this tool yet. In
>> > the meantime, I am also using other 3rd party tools (i.e. Photoshop and
>> > Snagit). I should add that as a best practice for PDF output, use vector
>> > images such as .eps or .svg whenever possible.
>>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
