RE: "usable" screen captures

Subject: RE: "usable" screen captures
From: john -at- garisons -dot- com
To: "Leonard C. Porrello" <Leonard -dot- Porrello -at- SoleraTec -dot- com>
Date: Mon, 15 Sep 2008 11:20:51 -0400 (EDT)

If translation is at all an issue, try to avoid using callouts as it
requires new screen shots as well as precise labeling, etc. And the
contents are hard to isolate for localization.

Leonord's suggestion is a good one.

John G

> I've used both approaches depending on the complexity of the screen. If
> you are writing procedures, you might also consider breaking the screen
> apart into smaller chunks, using a "big picture" screen shot at the top
> of a section and call-out screen shots in the step by step sections.
> Leonard


ComponentOne Doc-To-Help gives you everything you need to author and
publish quality Help, Web, and print content. Perfect for technical
authors, developers, and policy writers. Download a FREE trial.

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity!

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.


"usable" screen captures: From: Rob Hudson
RE: "usable" screen captures: From: Leonard C. Porrello

Previous by Author: Re: WaH
Next by Author: Re: OT RE: From the department of redundancy
Previous by Thread: RE: "usable" screen captures
Next by Thread: RE: "usable" screen captures

What this post helpful? Share it with friends and colleagues:

Sponsored Ads