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.
An excellent point. Maintenance costs also go way up when you use
From: john -at- garisons -dot- com [mailto:john -at- garisons -dot- com]
Sent: Monday, September 15, 2008 8:21 AM
To: Leonard C. Porrello
Cc: Rob Hudson; techwr-l List
Subject: RE: "usable" screen captures
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.
> I've used both approaches depending on the complexity of the screen.
> you are writing procedures, you might also consider breaking the
> apart into smaller chunks, using a "big picture" screen shot at the
> of a section and call-out screen shots in the step by step sections.
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-