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.
Does anyone have a workable standard for naming doc files?
The convention that we are using (by tradition) and considering (by
choice) is to name each file so it indicates only the chapter NAME
and the environment.
I've also used a convention where the name of the doc file
indicates the product, environment, guide, and chapter number.
For example, PPPDI04 would indicate the product (PPP),
environment (D=DOS), guide (I=Install), and chapter number
(04).
I liked this convention because it was always easy to tell if
you had all the files in a guide, and whether they were in the right
sequence in a master file (Word for Windows) or book file
(FrameMaker).
Any opinions on the matter? What do you do?
Doug Fettig
DFETTIG -at- NYD -dot- LEGENT -dot- COM
