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.
unix and other operating systems had long filenames long before
Macintosh. Some OSs are sensitive to case, so this is one consideration:
maintain the case of the original. In addition, some MS/PC-DOS
conventions of convenience or notation (I'm not sure if they're standards
adopted by some group or other) that refer to system files in all caps,
such as AUTOEXEC.BAT, CONFIG.SYS, FIND.EXE (files delivered with the
system), and user-created files in lower case. I'm not sure, but I seem
to recall one model that refered to executables differently from data
files, distinguishing by some form of capitalization.
On Sat, 23 Nov 1996, Walter L. Bazzini wrote:
> >> "Below admin.ini are the Group INI files which are named by the group,
> for example, staff.grp and library.grp." <<
> While we're more or less on the subject, is there a globally accepted, correct,
> set in stone convention for setting in text the names of files? I typically use
> all caps (CONFIG.SYS), and a different font from the body text. But nowadays --
> I guess all days, in Macintosh Land -- with long file names (filenames) and
> mixed case, am I just showing my age?
> --Walter L. Bazzini
> 73300 -dot- 111 -at- compuserve -dot- com