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.
> 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: "
>
> Each time a product name appeared it would be a pair with
> both elements condition tagged. [Prod1] would have condition
> notProductTwo, and [Prod2] would be tagged notProductOne.
>
> I would do the same with paragraphs and whole topics/pages
> that applied to just one or the other.
All together now: It depends. :-)
Do you (or will you potentially) have multiple deliverables to derive
from the single source, like print/PDF plus online help? What
application and version are you using?
In FrameMaker 7.x or earlier, conditions could only be ORed, so to AND
conditions, you had to define combination conditions, e.g., Prod1+Print,
Prod1+Help, Prod2+Print, Prod2+Help. If you add more products and/or
outputs, the number of combination conditions you need quickly becomes
large. FM 8 and 9 support logical expressions for what to show, so you
can show and hide any combination of conditions.
There's no reason to name the condition for the Prod1 text "notProd2"
unless it's easier for you to think of it that way and no one else will
ever need to understand it. Me, I'd want to tag the text for Prod1 as
"Prod1."
I second Tammy's warning about conditionalizing mid-sentence snippets --
it's much less error-prone and messy (and better for translation) to
conditionalize only complete sentences or paragraphs.
If you're using FM, you shouldn't use conditions for "Your
[Prod1][Prod2]..." anyway. Use variables for the product names, model
numbers, doc titles, etc. Then import one set of variable definitions to
output Prod1 deliverables and another set to output Prod2 deliverables.
If you're using Word, my sympathies. ;-)
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-777-0436
------
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-