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.
While dead-on accurate, I would wager that most computer users don't
know this. But that's really beside the point.
Getting nit-picky redlines back like this are an opportunity to
revisit your style guide and see if they are addressed in there or in
any other style guide you refer out to for specific conventions (such
as the Microsoft Manual of Style, which does cover this very subject).
On Thu, Nov 18, 2010 at 1:43 AM, Richard Mateosian <xrmxrm -at- gmail -dot- com> wrote:
> 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
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-