Skip to main content
N
naglists1-Visitor
1-Visitor
November 9, 2012
Question

Friday-brain algroup-fu #FAIL

  • November 9, 2012
  • 6 replies
  • 2218 views
It has been too long since I last algrouped and the geometry has fallen out
of my head. Somewhere I remember a drawing that depicted what each setting
controlled ... I need to get that done as a tattoo on the back of one of my
hands .... If I can find it.

Anyhow, I've got a three column algroup. I can get the first two columns to
display correctly. Or I can get the last two to display correctly.
(Correctly means they appear on the same line.)

Which measurement do I need to adjust below to get the third group to not
break to a new line? I've been adjusting the leftind for the third set
which displays task.txt.

<att>
<charsubset>
<indent leftind="-1in" rightind="6in" firstln="-1in"/">
<algroup refpoint="first"/">
<usetext source="actor.txt" placemnt="after">
<subchars>

<indent leftind="-1in" rightind="6in" firstln="-1in"/">
<quadding quad="left"/">
<textbrk startln="0" endln="0"/">
<algroup refpoint="first"/"></subchars>
</usetext>
</charsubset>
</att><att>
<charsubset>
<indent leftind="0in" rightind="5.8in" firstln="0in"/">
<usetext source="beforetext" placemnt="after">
<subchars>

<indent leftind="0in" rightind="5.8in" firstln="0in"/">
<quadding quad="left"/">
<textbrk startln="0" endln="0"/">
<algroup refpoint="first"/"></subchars>
</usetext>
</charsubset>
</att><att>
<charsubset>
<indent leftind=".5in" rightind=".2in" firstln=".5in"/">
<usetext source="task.txt" placemnt="after">
<subchars>
<indent leftind=".5in" rightind=".2in" firstln=".5in"/">
<quadding quad="left"/">
<textbrk startln="0" endln="0"/">
<algroup refpoint="first"/"></subchars>
</usetext>
</charsubset>
</att>

--
Paul Nagai

    6 replies

    N
    naglists1-VisitorAuthor
    1-Visitor
    November 12, 2012
    I figured out I have a different problem than I thought ... I paid too much
    attention to the first elements out of the gate.

    Is there a FOSI / algroup trick to allow subsequent elements that do not
    fit into the third algroup "flow" back into the first two without causing a
    line break at the top of the third algroup?

    For example, I have:
    <actor>
    <task_number>
    <task>

    And the first few lines of task fit within the third "column" but
    subsequent lines need to go to the left hand page margin overlapping the
    columns reserved for actor and task number. FOSI handles this but causes a
    line break on the first line of the task. Does that make sense?

    I get:

    OPERATIONS 1
    Do this thing
    Do that thing
    Issue this command

    1234 SADF wer sadf 1234 ASDF wer qwerty DDDDDDDD BBBBBBBB EEEEEEE

    Instead of:
    OPERATIONS 1 Do this thing
    Do that thing
    Issue this command

    1234 SADF wer sadf 1234 ASDF wer qwerty DDDDDDDD BBBBBBBB EEEEEEE




    P
    ptc-19080751-Visitor
    1-Visitor
    November 12, 2012
    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!"


    N
    naglists1-VisitorAuthor
    1-Visitor
    November 12, 2012
    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!"
    >
    P
    ptc-19080751-Visitor
    1-Visitor
    November 12, 2012
    Re: "Sometimes the data in <task> needs to be presented pgwide." By data, do you mean particular elements?
    N
    naglists1-VisitorAuthor
    1-Visitor
    November 12, 2012
    Yes, there are a handful of elements (<system_response> for example) that
    support pgwide="yes" and must begin at the left-most position for the page.


    On Mon, Nov 12, 2012 at 11:40 AM, Suzanne Napoleon <
    SuzanneNapoleon@fosiexpert.com> wrote:

    > Re: "Sometimes the data in <task> needs to be presented pgwide." By data,
    > do you mean particular elements?
    >
    > Re: "That's what's breaking the algroup on the third column ... forcing
    > content left overlapping algroups 1 and 2." Is this what you want?
    >
    > Suzanne
    >
    P
    ptc-19080751-Visitor
    1-Visitor
    November 12, 2012
    What is the flowtext column width?


    Terms & ConditionsAccessibility statement