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:Use of filenames/pathways in docs. From:NCSU Virology Lab <virus -at- MBIO -dot- MBIO -dot- NCSU -dot- EDU> Date:Thu, 12 Jan 1995 16:49:36 GMT
I am writing two in-house documents for running two software packages
our organization uses, directed at instructing the user on how to
manipulate the packages as the company uses them. In writing this,
I have come into several instances where I must ask the user to
specify a filename and pathway. In many cases, the filename/pathway
information is variable, depending on which function the operator
wishes to use. Since these documents will be going into the Quality
Procedures Manual for an ISO-9002 registered company, the QC super-
visor is very interested in writing these instructions in proper
Therefore, my question is this: What is the proper way to represent
a filename, pathway, etc. in written English? Is there an accepted,
standard format? If you know, please respond via email to this