Hi Suzanne,
All content is suppressed and expressed in algroups. The first column is a
simple text save for the <actor> element. The second column is the task
number, just a text counter tracking the occurrence of <task>. The third
column is the contents of <task> which can be complex. Multiple <para>
<note> <list> etc. etc. etc. Sometimes the data in <task> needs to be
presented pgwide. That's what's breaking the algroup on the third column
... forcing content left overlapping algroups 1 and 2.
Am contemplating, but have not tried, putting only the first child of task
into the algroup and putting the rest into a text column beginning at the
same position as the 3rd algroup. If I can work that out from a savetext
perspective I'm pretty sure the formatting will be "easy." But that's how
things always look when you're imagining them 😉
On Mon, Nov 12, 2012 at 10:37 AM, Suzanne Napoleon <
SuzanneNapoleon@fosiexpert.com> wrote:
> Paul,
>
> I'm not certain what you're trying to do, but if the problem is the
> placement of <task_number>, I suggest suppressing and saving it for output
> in the next column. There would be two algrouped columns instead of three.
>
> HTH.
>
> Good luck!
> Suzanne Napoleon
> www.FOSIexpert.com
> "WYSIWYG is last-century technology!"
>