This document discusses strategies for using conditional text in FrameMaker 8, including marking up text with condition tags or attributes, and filtering content based on attribute values. It provides an overview of using traditional condition tags versus attribute filtering, and demonstrates how to apply both show/hide conditions and conditional expressions in regular FrameMaker as well as attribute filtering in structured FrameMaker. The presenter is a technical consultant and FrameMaker expert who provides information on effectively using conditional text functionality in both unstructured and structured FrameMaker documents.

1. Strategies for Conditional Text
in FrameMaker 8
Terry Smith
DITA/TECHCOMM
November 2008

2. About the presenter
Technical Consultant, Scriptorium Publishing,
based in Research Triangle Park, NC
FrameMaker ACE
Authored updates to Publishing Fundamentals:
FrameMaker 8

3. Agenda
Purpose of conditional content
Marking text as conditional
Options for processing conditional content in
unstructured FrameMaker
Attribute filtering in structured FrameMaker

5. Determine the conditional
text “dimensions” you need

6. Which content can be
conditional?

7. Marking conditional content
in regular FrameMaker
Choice 1: Never allow condition tags to overlap
Choice 2: Always (or just sometimes) allow
overlapping condition tags

8. Regular FrameMaker
Show/Hide conditions: Each condition is either
showing or hidden (despite misleading
Conditional Text dialog box that implies other
options).
Conditional expressions: These let you combine
conditional operators (those used in Boolean
expressions) for more flexibility.

9. Traditional conditional text:
applying one tag only
Good: Easy to see which condition tags are
applied.
Bad: May need lots of condition tags.

10. One tag only: up to 32
condition tags needed

11. Traditional conditional text:
layering every condition tag
that applies
Good: May need (somewhat) fewer tags.
Bad: Difficult to manage the tags.

12. Layering condition tags: only
18 tags (not 32)

13. Layered tags hard to manage

14. Demo of Show/Hide
conditions
Applying conditions
Show/Hide
Showing condition indicators

15. Conditional expressions
require minimum number of
condition tags

16. Conditional Expressions
Mix of condition tags (some layered, some not)
= Challenging conditional expressions
Consistently layered tagging = easy conditional
expressions

17. Demo of conditional
expressions
Building an expression
Showing “as per expression”

18. Condition tags retained in
XML, but not part of
structure

19. Structured FrameMaker
Attributes and filtering available for structured
FrameMaker only.
Filter which conditional content shows in
output based on attributes.
Filtering is at the element level.

20. Marking conditional content
in structured FrameMaker
Specify only one value for a single attribute.
You can specify values for multiple attributes.

21. Attribute filtering goes beyond
conditional text functionality
Can filter on multiple attributes.
Product = “Pro” AND Output = “Print” AND
Platform = “UNIX”
Conditional tags are always combined as OR.
Excellent approach for content with numerous
conditions.

22. Downside: Visual indicators
not available
You Cannot use colors to indicate attribute
filtering unless you add on to FrameMaker:
ABCM
Sourcerer
Custom FDK client
FrameScript

23. Structured FrameMaker
setup
Your document's structure must allow some
attributes you can use for your conditional
content.

25. Add attributes for filtering
to EDD
Add attributes to all elements you may want to
make conditional.
For XML, you need to change the files that
make up the structured application to process
any attributes you add.
No additional changes needed for print and
PDF (Save As PDF).

26. Marking structured content
as conditional
Specify one value for attribute.
Structure may allow multiple values for a single
attribute, but filter by attribute doesn’t process
multiple values on a single attribute.
You can specify both condition tags and
attributes, but you can only use one to set
which conditions show in FrameMaker.

27. Demo of filter by attribute
Specify attribute values.
Build filter.
Apply filter.
Validate for each attribute filter.

28. Contact information
Scriptorium Publishing
Research Triangle Park, NC, USA
www.scriptorium.com
tsmith@scriptorium.com
919-481-2701, x113