> From: Gabor Kovesdan [mailto:[email protected]]
>
> > Why is a substeps wrapper required for the second case? Most likely
> > to avoid confusion.
>
> Thanks Bob, it looks now somewhat better, yet there's still an ugly case. If I
> want to insert stepalternatives between two steps, I can only do it if I wrap
> it
> into a step, otherwise the FO file will be invalid.
It might help to back up and consider what stepalternatives is for: to indicate
that exactly one of the steps in the set should be performed:
<step><para>Get a loaf of bread</para></step>
<step><para>If they have eggs, get a dozen</para></step>
<step>
<stepalternatives>
<step><para Condition="not-funny">Get a dozen eggs</para></step>
<step><para Condition="funny">Get a dozen loaves of
bread</para></step>
<step><para Condition="likely">Forget to go to the
store</para></step>
<stepalternatives>
</step>
If you have steps like this:
1. Do part A
2. Do part B
3. If you can't do part B, do part C
You might want to code that as:
<step>
<para>Do part A</para>
</step>
<step>
<para>Do one of these:</para>
<stepalternatives>
<step><para>Do part B</para></step>
<step><para>If you can't do part B, do part C</para></step>
<stepalternatives>
</step>
When used as originally intended, it is semantically clear and not uglier IMHO
than any other XML. Hope this helps.
Regards,
Paul Bort
TMW Systems, Inc.
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
