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.
Yes, though depending on how extensive the differences are variables
might be easier than conditional text.
On Tue, Dec 22, 2009 at 12:34 PM, McLauchlan, Kevin
<Kevin -dot- McLauchlan -at- safenet-inc -dot- com> wrote:
>
> For a doc set that can be used with either Prod1 or
> Prod2, can I get away with just two condition tags:
>
> - notProductOne
> - notProductTwo
>
> Example text would be something like:
>
> "Your [Prod1][Prod2] arrives from the factory with default
> network settings. Before using the appliance configure
> for your network as follows: " ...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Help & Manual 5: The all-in-one help authoring tool. True single- sourcing --
generate 8 different formats and as many different versions as you need
from just one project. Fast and intuitive. http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
