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:FrameMaker and conditional text From:cll01821 -at- lycos -dot- com To:thejavaguy -at- gmail -dot- com Date:Sat, 07 Jan 2006 09:30:40 -0500
Just curious ... did you consider generating two separate guides?
I'm currently generating 11 "separate" install guides from one set of source files. I create a book file for each platform-specific guide. Each book file contains the appropriate chapters for the platform; for example, some of the books use "Installing the TWAIN driver" while others use "Installing the JAR file".
Some chapters, such as "Installing the software" contain a combination of common and unique text; I apply conditional tags as needed to the platform-specific text or images. For example, step 6 might document how to license a device. The step contains all the information for licensing devices for all platforms, but I've applied a conditional tag to each bit of platform-specific information.
In addition, I do violate one of the "rules" of conditional text by applying conditional tags within a sentence. For example, if a sentence relates to platform x and platform y, I might writing On platformxplatformy, do this, with appropriate tags applied to "platformx" and "platformy". (I try to avoid doing this as much as possible because it makes localisation a wee bit more complex.)
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-