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.
Just a side note: I quit putting commands in quotes awhile back. I now
use bold or italic for the very reason you mention--I kept having users
trying to type in the quotes. Well, it solved the problem.
Melonie R. Holliman
Technical Writer
CPD Marketing
Advanced Micro Devices
> -----Original Message-----
> From: Fred Sampson [SMTP:wfreds -at- CRUZIO -dot- COM]
> Sent: Wednesday, June 30, 1999 11:28 PM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Re: Editor Please....
>
> Lisa:
>
> This subject created ongoing discussion between me and my supervisor a few
> months ago. He accepted the Microsoft Manual of Style for Technical
> Publications as gospel, except on this one. He was afraid that a user
> would
> type *arrgh.* (including the period) if we told the user to type "arrgh."
> instead of "arrgh". I think this came from his background in programming ,
> in which every bit of punctuation means something. Not that it doesn't
> mean
> anything grammatically. He also thought the period inside the quotation
> marks "looked funny." I think it looks funny with the period outside the
> quotation marks. But, that may be because I know what the convention is.
>
>
