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:Re: Documentation Estimates From:Coleen MacKay <cmackay -at- BNA -dot- COM> Date:Mon, 28 Nov 1994 12:19:35 EST
I think that indexing figure you refer to is for the
work of a human indexer. 5 pages per hour is about right.
No indexing utility provides anywhere near as useful or
comprehensive an index as a trained human indexer can.
(Yes, I have been an indexer for several years, and have
just recently taken up tech writing. I have now officially
BTW, many of the issues discussed on this list about getting
respect for the profession are common laments of indexers.
Creating a good index requires training and experience.)
cmackay -at- bna -dot- com
>> Chuck Martin commented on these figures:
>> Indexing: 5 pages per hour
Rick Lippincott asked:
>>I'm curious, though, about the rate for "indexing." Using
>>an indexing function on FrameMaker, I can apparently work
>>much faster than that. On the othe hand, certain parts of
>>the task are "invisible", setting up the properly coded
>>info in the text ahead of time. Has the estimated time for
>>indexing gone down? Or is it just moved to a different
>>location? What's the opinion on this?