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.
Subject:Indexing From:Mike Bygrave <bygravem -at- INTUITIVE -dot- CO -dot- UK> Date:Wed, 26 Jun 1996 10:29:32 +-100
Scribes of the world,
I have a question about indexing strategies in procedural, task-oriented
software documentation. However, before I start, I would like to make it
clear that I hate indexing more than I hate many, many things and,
therefore - while I want a complete and useful index as an outcome - I
don't want to spend much time doing it (I'd rather spend the time pulling
my own fingernails out - it's more pleasant).
So, here's the question: should general index tags have initial caps? I've
just rummaged through our departmental bookshelf, and opinions seem to be
split. Microsoft manuals use lower case in their indices (bad source), and
so the Chicago Manual of Style (reasonable source). However, a number of
equally high-profile 'tomes' use initial caps in their indices.
I must admit, I naturally tend towards the use of lower case index tags - I
use W4W, and most of the terms I want to index appear in lower case.
However, I'm quite prepared to bow to the infinite wisdom of list
Mike Bygrave (bygravem -at- intuitive -dot- co -dot- uk)
"1966 was a great year for English football - Cantona was born."
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-