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.
For toolbar button graphics, prefix with b_. For example, b_copy.gif.
For dialog boxes, prefix with d_. For example, d_save_file.gif.
For icons (on tree controls, status bars, desktops, etc.), prefix with (you
guessed it) i_, as in i_connected.gif.
Guess what I use for menu graphics!!!
Beyond that, I might categorize in subdirectories if the program is somewhat
modularized.
Beyond *that*, I don't try to be brief, because the more you try to
abbreviate, the more confused you will get. I once worked with a program
that had something like 900 graphics that we used screen captures of. To
make matters more interesting, I originally documented it in Windows 3.1. So
I had 900 .bmp files I had to come up with 8-character names for. I used a
convention similar to the ones above (b_ etc.) to categorize them by type,
and I used subdirectories, but I still had to come up with 6-letter
abbreviations for all those files. Ended up with stuff like i_stpt1p.bmp.
Nightmare.
Good luck, hth
Melissa Fisher
melissa -dot- fisher -at- delta-air -dot- com
(404) 773-8674
> -----Original Message-----
> From: Kimber Miller [mailto:kimber_miller -at- acs-inc -dot- com]
>
> Your opinion or experience sought with naming conventions for
> the scads
> of images one produces when putting together software user
> documentation.
>
