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.
On Jul 2, 2:11pm, Tamminga, Ernie wrote:
<SNIP>
> But extremely often in tech-writing, a phrase we're placing within
> quotes is some kind of computer command. Usually the comma is NOT a part
> of the command itself, and can easily cause confusion if it's included
> within the quotes. So I always put the trailing comma outside the
> quotation marks. For example:
>
> If you enter the command "GO TO TOP", the program will set your
> monitor on fire.
>
>-- End of excerpt from Tamminga, Ernie
I've been struggling with how to set commands off from body text for years
now. I'm just curious about why you would use quotation marks in the above
example; doesn't the use of full caps set off the command well enough? If you
avoided using quotation marks for commands, you wouldn't have the comma
problem.
--
Danny Wood
dwood -at- ssi -dot- navtech -dot- com
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
