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.
Digester late to this discussion. Therefore random thoughts.
Regarding UNIX--ignore at your peril. Your server may be NT today but could
be UNIX next week. Do you want to have to rename all your files when that
happens? Biggest problem I see with (most, I guess) UNIX is not with
filename length but rather with use of mixed case in filenames. NT ignores,
but this is important to UNIX. Suggest all lower case.
While "chapter" may be a valid concept, "page number" is not on the internet
or on an intranet. Think ahead and assume the web is where your document
will be someday if it isn't already.
My suggestion is to name the graphic to describe what it is and not where it
is used. If your document will never (?) change, "figure4-3.gif" is then
fine, because in one sense that's what it is. Since the writer that follows
you will learn your document and your "convention" from scratch anyway, I
wouldn't worry too much about conventions.
Image1.gif, image2.gif, etc. is what you get when you save a Word document
as html. What else could they do? Assume you have to change the names.
