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.
I personally avoid using spaces and underscores in file names. Some
software packages have difficulty recognizing file names with spaces;
this can be a particular difficulty for files when they are published
on an external website, so it is best to avoid using spaces. Using
underscores and hyphens in your file names increases the length. I use
capital letters to delimit words. By using capital letters to
differentiate between the words the file name is still readily
recognizable. Where capitalized acronyms are used in file names, the
acronym should appear in capitals and the first letter of the
following word should also be capitalized.
On 3/20/08, Combs, Richard <richard -dot- combs -at- polycom -dot- com> wrote:
> Ronquillo, Michael wrote:
> > How does everyone feel about putting underscores between
> > words when naming files and folders? For example
> > This_Is_an_Example.doc
> > Is this necessary or subjective? How do you feel about
> > capitalizing the words as if it was a title?
> I agree with Fred about spaces and underscores. Spaces are a bad idea,
> even in Windows -- if a path (say, for a shortcut, in a batch file, or
> at the command prompt) contains spaces, you have to remember to enclose
> it in quotes.
> As for underscores, I've never understood the preference among geeks for
> underscores over hyphens. I don't think a_really_long_file_name.ext is
> any more readable than a-really-long-file-name.ext, and in some
> situations less. Plus, it's harder to type.
> I don't usually capitalize file names, and certainly don't use
> camel-caps. Just more pointless pressing of the Shift key.
> IMHO. FWIW. YMMV.
> Richard G. Combs
> Senior Technical Writer
> Polycom, Inc.
> richardDOTcombs AT polycomDOTcom
> rgcombs AT gmailDOTcom
> Create HTML or Microsoft Word content and convert to Help file formats or
> printed documentation. Features include support for Windows Vista & 2007
> Microsoft Office, team authoring, plus more.
> True single source, conditional content, PDF export, modular help.
> Help & Manual is the most powerful authoring tool for technical
> documentation. Boost your productivity! http://www.helpandmanual.com
> You are currently subscribed to TECHWR-L as ash -dot- lovely -at- gmail -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit http://lists.techwr-l.com/mailman/options/techwr-l/ash.lovely%40gmail.com
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-