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.
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.
The ellipsis is not part of the command name. It is a reassurance in
the UI that tells users that clicking that command won't cause a
precipitous action until they have had a further opportunity to
specify what they want to do. No such reassurance is needed in the
manual. ...RM
On Wed, Nov 17, 2010 at 9:44 PM, Tony Chung <tonyc -at- tonychung -dot- ca> wrote:
> I don't see why you wouldn't want to recreate the UI as closely as possible.
--
Richard Mateosian <xrm -at- pacbell -dot- net>
Berkeley, California
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-
