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.
Subject:Re: periods inside quotation marks? From:Scott Miller <smiller -at- CORP -dot- PORTAL -dot- COM> Date:Tue, 9 Jun 1998 09:19:23 -0700
Agreement here with Janice, for the following reasons:
1. There's no need for the quotation marks. Button names should use caps
for every word, they're usually short, they're preceeded by the verb
"click," so they can hold their own in a sea of text. I can almost see
the need for quotation marks around long dialog box options such as the
"Send this message in rich text format" checkbox, but not for little ol'
buttons.
2. There's no need to include the "..." in the button name. The "..." is
just an indication that the button opens a dialog box, and the user can
get that info from the UI itself. Including it in the docs just makes
things hard to read.
- Scott Miller
smiller -at- portal -dot- com
------------------------------------------------------------------------
> Piece of advice number 1, change your house style so button
> names don't have to go inside quotation marks!
>
> Piece of advice number 2, make it your house style that you
> don't have to include ellipses that appear next to a button
> name when you are referring to the button in text.
>
> If number 1 doesn't work, I would put the period outside
> the quotation marks, since this is not a quotation but a "name"
> of something.
>
