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: File names in text From:"Virginia L. Krenn" <asdxvlk -at- OKWAY -dot- OKSTATE -dot- EDU> Date:Wed, 22 Mar 1995 14:58:01 -0600
When I was documenting my programs in Script (which didn't have font
choices), I used capital letters (first letter only) to identify file
names.
For example:
Copy the Payroll file to the Master data base. I felt that identified
the word as being a proper name rather than an adjective.
Virginia Krenn
asdxvlk -at- okway -dot- okstate -dot- edu
______________________________ Reply Separator _______________________
Subject: File names in text
Author: Karen Kay <karenk -at- netcom -dot- com> at SMTP
Date: 3/18/95 12:28 PM
We've talked about how we include commands in text talking about the
command (in Courier, or on a separate line). I'm editing something now
that mentions a lot of different file names, some with extensions
and some without. Normally, I'd set these off in Courier, just for
clarity, to distinguish them from the text. BUT--this stuff is all
done in ASCII, so I can't use font changes to distinguish anything.
I've decided to use single quotes, because a) I feel like I have to do
something, b) I think they are less intrusive than double quotes, c)
double quotes are used elsewhere for real quoting.
