Skip to main content
P
ptc-9533431-Visitor
1-Visitor
September 16, 2010
Question

Displaying [Continued] for a procedure that breaks pages?

  • September 16, 2010
  • 8 replies
  • 1456 views
I have a requirement to create a [Continued] mark at the bottom of a page
when a procedure breaks across pages. I've got no idea on how to make this
happen with a FOSI, any ideas?

The printed sample I have looks like the marking may be placed in the
footer so it is always in a consistent location at the bottom of the page
rather than floating to the point where the text breaks. Not sure if this
is a hard requirement or if either method is harder/easier to accomplish.

..dan

    8 replies

    L
    LynnHales1-Visitor
    1-Visitor
    September 16, 2010
    Dan,

    This works to put a 'continued' at the top of the page.

    You may want to look at the 'floatloc' to see if it can go at the bottom of the page. I think it can. Also take a look at the 'botfloat' attribute on the <flowtext> and the <rectopg>, <versopg>, and <blankpg>. If you set the 'botfloat' to the 'floatid' for your continued text, it SHOULD show up there.

    <floatloc floatid="subsubtasktitlcontd" floattyp="atpgbrk"&lt;br"/>maxdepth="24pt" minspace="0" nomspace="0" maxspace="0">


    <charsubset>
    <usetext source="\ASSEMBLY" and=" preparation=" for=" use–=" continued\&quot;=">
    <subchars charsubsetref="titlesub">
    <float flidref="subtasktitlcontd" width="page" scope="acptrejinsp"&lt;br"/>pagetype="next"></subchars>
    </usetext>
    </charsubset>


    Lynn


    ---- Dan Vint <dvint@dvint.com> wrote:
    > I have a requirement to create a [Continued] mark at the bottom of a page
    > when a procedure breaks across pages. I've got no idea on how to make this
    > happen with a FOSI, any ideas?
    >
    > The printed sample I have looks like the marking may be placed in the
    > footer so it is always in a consistent location at the bottom of the page
    > rather than floating to the point where the text breaks. Not sure if this
    > is a hard requirement or if either method is harder/easier to accomplish.
    >
    > ..dan
    >
    P
    ptc-9533431-VisitorAuthor
    1-Visitor
    October 5, 2010

    I've been trying to work this example for my particular problem and it doesn't seem to be working. I probably have missed a detail or a wrong value for my use.

    Couple of questions than I'll tell you my results. So there is a botfloat value just like there is a topfloat. So that seems obvious. What I'm not sure of is the proper location to apply the float. So it can be defined on a page description or can be set on the flowtext and the column element within it. I have a single column document, does it matter where I define this float?

    so my XML looks something like this:

    <chapter>

    <section><title>text</title>

    <procedure>

    <step>a step</step>

    <step>a step</step>

    <step>a step</step>

    </procedure>

    </section>

    <section><title>text</title>

    <procedure>

    <step>a step</step>

    <step>a step</step>

    <step>a step</step>

    </procedure>

    </section>

    ...

    </chapter>

    I'll shwo the FOSI stuff net, but I have tried to define this float to affect the procedure element, becasue when on of 'its steps breaks to a new page, I want the bottom of the first page to have the word (actually a graphic) showing CONTINUTED->. It seems like the float is gathering all the content of each procedure and doign two things:

    1) always printing CONTINUED even if the procedure didn't break

    2) Content is over flowing the page, so there is no break if it does span a page

    3) The procedure content is being moved past several of the section titles. So now I get the ttitle and any text that might come before the procedure - I'll get several of these before the first procedure actually prints and it is run off the bottom of the page with an overset

    FOSI Stuff

    <floatloc floatid="continued.bottom" floattyp="atpgbrk" maxdepth="0pt"&lt;br"/>minspace="13pt" nomspace="13pt" maxspace="13pt">

    <charsubset charsubsetid="continued">
    <float flidref="continued.bottom" width="page" pagetype="next">
    <usetext source="\CONTINUED\">
    <subchars>
    <float flidref="continued.bottom" width="page" scope="acptrejinsp"&lt;br"/>pagetype="next"></subchars>
    </usetext>
    </charsubset>

    <e-i-c gi="procedure">
    <charlist charsubsetref="block" continued&quot;=">

    <reset resetlist="procedurect"></charlist>
    </e-i-c>

    Now I've placed the float here with fewer bad pages produced:

    <region xoff="0in" yoff="-0.04in" width="8.5in" height="11in"&lt;br"/>valign="middle" rotation="0" layer="-2">
    <putgraph graphname="right-front-cl"></putgraph>
    </region>
    <flowtext numcols="1">
    <column width="4.0in" botfloat="continued.bottom"></flowtext>
    </pagespec>
    </rectopg>

    And I've placed it on the pagedesc with worst results:

    <rectopg width="8.5in" nomdepth="11in" bind="lleft" chgmkplc="pright"&lt;br"/>topfloat="table-title.top" botfloat="continued.bottom" maxfloatpct="100" xvjstretch="max">

    Any idea what I'm missing or messed up?


    B
    bibach1-Visitor
    1-Visitor
    October 5, 2010
    Hi, Dan...

    I think the problems lie in the definition of the "continued"
    charsubset. The first <float> category, being at the top level, will
    apply to the procedure, itself, rather than just to the "CONTINUED"
    footer. This would explain why the procedure contents are showing up
    out of order and running off the page, since they're being forced into
    the float area.

    Also, I think you need to change the "scope" characteristic from
    "acptrejinsp" to "procedure" so that the CONTINUED footer is
    terminated at the end of the procedure, even if that means it never
    shows up at all, because the procedure doesn't cross a page boundary.

    Standard disclaimers apply, of course: theories untested, YMMV. 🙂

    -Brandon 🙂


    P
    ptc-9533431-VisitorAuthor
    1-Visitor
    October 5, 2010
    > Hi, Dan...
    >
    > I think the problems lie in the definition of the "continued"
    > charsubset. The first <float> category, being at the top level, will
    > apply to the procedure, itself, rather than just to the "CONTINUED"
    > footer. This would explain why the procedure contents are showing up
    > out of order and running off the page, since they're being forced into
    > the float area.

    Ok, I'll buy that but what do I attach it to? I tied it to procedure
    because that is what I want to detect breaking across pages, nothing else
    would give me that condition.


    >
    > Also, I think you need to change the "scope" characteristic from
    > "acptrejinsp" to "procedure" so that the CONTINUED footer is
    > terminated at the end of the procedure, even if that means it never
    > shows up at all, because the procedure doesn't cross a page boundary.

    I was going to ask what "acptrejinsp" was, it looked cryptic enough to be
    a FOSI value 😉 I tried looking for it in the spec but nothing came up in
    my search - now I know why.

    >
    > Standard disclaimers apply, of course: theories untested, YMMV. 🙂

    So I don't know what the first correction should be, I made the second one
    and I'm getting the same result. FYI, making the last change now has
    removed the CONTINUED label from the output but the editor still shows the
    generated text. It also looks like the float is accumulating all the
    procedures content, not just the current one.


    >
    > -Brandon 🙂
    >
    >
    B
    bibach1-Visitor
    1-Visitor
    October 5, 2010
    On Tue, Oct 5, 2010 at 2:34 PM, Dan Vint <dvint@dvint.com> wrote:
    >> Hi, Dan...
    >>
    >> I think the problems lie in the definition of the "continued"
    >> charsubset. The first <float> category, being at the top level, will
    >> apply to the procedure, itself, rather than just to the "CONTINUED"
    >> footer. This would explain why the procedure contents are showing up
    >> out of order and running off the page, since they're being forced into
    >> the float area.
    >
    > Ok, I'll buy that but what do I attach it to? I tied it to procedure
    > because that is what I want to detect breaking across pages, nothing else
    > would give me that condition.

    Sorry, I wasn't clear. I think you just need to remove the first
    <float> from the definition of "continued". You want to float the
    "CONTINUED" footer (which is done by the second <float> in that
    definition) and nothing else.

    -Brandon 🙂
    P
    ptc-9533431-VisitorAuthor
    1-Visitor
    October 5, 2010
    >
    B
    bibach1-Visitor
    1-Visitor
    October 5, 2010
    On Tue, Oct 5, 2010 at 3:17 PM, Dan Vint <dvint@dvint.com> wrote:
    > It made sense the second time I looked at it. Problem was I was editing in
    > the FOSI panels and this second one was being hidden - wasn't looking at
    > the raw code.
    >
    > Well that got rid of the accumulation of the procedure text but I also
    > don't have the CONTINUED being produced.

    Okay, a few more tweaks:

    1. Try setting maxdepth on floatloc to something more than 0pt, or
    just remove that attribute altogether.
    2. Set pagetype on float to "same" instead of "next".
    3. Setting botfloat="continued.bottom" on rectopg (and other rectopg
    and versopg siblings) should work.

    I was able to get this working on an orderedlist in an AXDocbook
    article. I applied code pretty much like what you had, with the
    mentioned changes, to a FOSI exported from the out-of-the-box Styler
    sheet.

    -Brandon 🙂
    P
    ptc-9533431-VisitorAuthor
    1-Visitor
    October 6, 2010

    After making the final changes Brandon recommended I had one last problem to fix. I had the placement set to after, changing that to before got the reults that I wanted.

    Thanks all

    ..dan

    In Reply to Brandon Ibach:

    Terms & ConditionsCookie settingsAccessibility statement