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.
This is what we're doing now. Since our printed "manual" is a pictorial hookup
guide on a foldout card and the rest of the user instructions are displayed on
the products' onboard CGD, CD-installed help or the Web, telling users to
"select <picture of button>" enables even readers who can't read the text to
find the right button by visual pattern-matching, and for localized product we
just need to have images of the translated buttons for the XML to display.
UI-based tech support calls are now at an all-time low.
----- Original Message -----
From: "Richard Mateosian" <xrmxrm -at- gmail -dot- com>
> It's clearer not to do so. Otherwise, why not show a screen shot of
> the name in its menu context rather than just a text version of the
> name? These shots would recreate the UI more closely, but they would
> make your manual confusing to read.
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-