RE: "usable" screen captures

[john -at- garisons -dot- com]

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.
http://www.componentone.com/DocToHelp/

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

---
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 http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


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
http://www.techwr-l.com/ for more resources and info.