Re: Getting quality screen shots for documentation

[dr2@xxxxxxxx]

OK, to get get if the skrunching of the screen from an alt-printscrn, I
open a .doc, go to LAYOUT, Change the orientation to LANDSCAPE and the
Margins to NARROW, then CTL-V the screen onto my .doc and adjust what I
need to there... 

for what it's worth...

On 2023-05-23 14:41, Peter Dow wrote:

> If you're just doing screen shots of green screen stuff, how about STRCPYSCN?
>
> It makes a copy of all screen images in a physical file until an ENDCPYSCN is issued.
>
> --
> *Peter Dow* /
> Dow Software Services, Inc.
> 909 793-9050
> petercdow@xxxxxxxxx
> pdow@xxxxxxxxxxxxxx /
>
> On 5/22/2023 5:23 PM, Reeve wrote: 
>
> > I'm having trouble with low-quality screen shots in my printed (PDF)
> > documentation.
> >
> > I have a big, high-resolution monitor for 132-column screen formats with
> > the Andale Mono font and use SnagIt to get full-screen images as .jpg's.  I
> > don't do any post-processing (like stripping out colors).  I drop the plain
> > jpg's into Madcap Software's "Flare" single-source authoring tool and get
> > HTML, PDF, and Word (to name a few).  In HTML format, the images (1536 x
> > 840 pixels) are good.  In Word and PDF format, they're not good at 660 x
> > 355 pixels.
> >
> > The Word and PDF quality was fine when I used Client Access.  The
> > degradation in image quality was immediately obvious when the Java-based
> > emulators took over--it was a gut punch and the only time I remember the
> > replacement product being worse than the original (and I used WDSC).  I had
> > a flashback to the days I was forced to use a Decision Data 5250 knockoff.
> >
> > I'd be grateful to hear how others deal with image quality issues (short of
> > installing Client Access on a Windows 10 box, or maybe with a Win 7 VM).
> > I'm considering 3rd party emulation and Photoshop-type applications.
> >
> > Thanks!
> >
> > -rf