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 for Component Software From:Melissa Fisher <mfisher -at- MOBSEC -dot- COM> Date:Fri, 9 Jan 1998 12:47:42 -0500
> I'm sure I won't be the first or last to suggest this to you, but I
> would use
> FrameMaker and the conditional text feature to accomplish your needs.
> You can assign conditional text tags to the text that is specific to
> particular components. You can show or hide each tag to create
> customized docs. If there are a limited number of combinations, you
> can
> set up templates to create books for different combinations of
> components.
>
> FrameMaker gives you a lot of options with conditional text, and it's
> a
> pretty stable feature for the most part. I'd be happy to answer any
> questions you have off-line to the best of my ability; also the
> Framers list
> is a good source of info about conditional text and Frame in general.
>http://www.frameusers.com for more info.
>
> HTH, and good luck
>
> Melissa Fisher
> mfisher -at- mobsec -dot- com
>
