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'm actually talking about summaries of all the chapters at
> the beginning of the document. The ones right before the
> chapter begins tend to be updated, because they're more noticeable.
Ah, I see. I misunderstood -- sorry!
What you're describing is something I might be persuaded to ditch -- but
first I'd ponder the purpose and how much pushback you might get. How
detailed are these summaries? What value do they add? Is it possible to
<gasp> ask users what they think? ;-)
Here's another thought: If the descriptions that start each chapter are
kept up-to-date, can you use the same text for the front-of-book
descriptions? And automate it?
For instance, in FrameMaker you could build the front-of-book summaries
from cross-references using the <$paratext> building block, so the
entire pgf (or two or three) that introduces the chapter is copied
automatically to the summary doc. Once these cross-references are in
place, any changes to the source pgfs will be reflected in the
front-of-book summaries as soon as the xrefs get updated.
Something similar can probably be done in Word using field codes, but
it's been a long time since I did any serious work in Word. :-}
HTH!
Richard
------
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-777-0436
------
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-