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.
Bingo bango bongo. Thanks for looking it up. I didn't have my MMOSFTP3
handy but knew it was in there.
On Thu, Nov 18, 2010 at 10:39 AM, Pro TechWriter
<pro -dot- techwriter -at- gmail -dot- com> wrote:
> The Microsoft Manual of Style for Technical Publication (Third Edition, page
> 181) says never to include the ellipsis. It uses Open as the example, as
> well.
>
> And I quote:
>
>
> (Excerpted) In general, avoid using an ellipsis(...) except in syntax lines
> or to indicate omitted code in technical material... In the user interface,
> the ellipsis is typically used to show truncation, as in a program name, or
> to indicate on menus and dialog boxes that a dialog box will appear to
> obtain more information from the user. Do not use an ellipsis in this
> context in documentation.
>
> *Correct*
> On the *File* menu, click *Open*.
>
> *Incorrect*
> On the *File* menu, click *Open*....
>
>
> The Microsoft Manual of Style is a great reference to have for any writer
> and is well worth the money.
>
> Best,
> PT
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-
