Re: FM+SGML: Conditions and attributes?

[Dan Emory <danemory@xxxxxxxxxxxx>]

But the approach described by Eric Dunn below wouldn't work when only part 
of the text within a paragraph is conditionalized. And if the conditional 
text spans the contents of multiple elements, you'd have to set the 
condition attribute in each of those elements. Furthermore, almost any 
element containing text, graphics, tables, table components, 
cross-references, etc. may be a candidate for conditional text. Thus, it 
seems to me that a single pair of elements marking the beginning and end of 
a conditional text instance is much simpler, easier to implement, and 
probably more amenable to automation with a Framescript or an API.

At 03:38 PM 11/22/01 -0500, edunn@transport.bombardier.com wrote:


>How about taking a similar approach and identifying which elements may be
>conditionalised and adding a condition attribute to those elements?
>This would control which information/content could be conditional. Framescript
>should still be able to apply/preserve the conditional tagging.
>
>Eric L. Dunn
>

====================
| Nullius in Verba |
====================
Dan Emory, Dan Emory & Associates
FrameMaker/FrameMaker+SGML Document Design & Database Publishing
Voice/Fax: 949-722-8971 E-Mail: danemory@primenet.com
177 Riverside Ave., STE F, #1151, Newport Beach, CA 92663
---Subscribe to the "Free Framers" list by sending a message to
majordomo@omsys.com with "subscribe framers" (no quotes) in the body.



** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **