Skip to main content
A
Anonymous
July 25, 2012
Question

Building tables as generated text from save/usetexts - page breaks?

  • July 25, 2012
  • 17 replies
  • 2996 views
Ok, so I have a series of small output docs (three elements within a wrapper, all wrapped in a root element) that I print in tabulated form.

I have these values aggregating into a savetext that eventually outputs a table as part of a usetext at the end of the document.

Since upgrading from 5.3 to 5.4, I have come to find that if the amount of content is more than a page-full, my table no longer breaks to another page (runs through the footer and throws my favorite error, page overset fault).

Has anyone else had this issue? Any clues here?

I have checked all the e-i-cs for table markup, for the document elements themselves, and the pseudo-element used to generate the text, and I have no explicit keeps set anywhere. I'm just at a loss as to what might have happened. I know I'm not the only one building tables in gentext, so perhaps someone else has seen something?

Thanks,

-Jason

    17 replies

    C
    ClayHelberg18-Opal
    18-Opal
    July 25, 2012
    Hi Jason--



    Have you tried fiddling with the deepcontentsplitting preference? IIRC,
    between 5.3 and 5.4 was about the time they either added or
    significantly improved that feature.



    --Clay





    Clay Helberg

    Senior Consultant

    TerraXML


    A
    Anonymous
    July 25, 2012
    Yup, gave that a shot, no luck with any of the three settings in 5.4

    It just acts like it's "stuck". There isn't one setting I have been able to adjust that makes any impact on the pagination of this generated table.
    P
    ptc-19080751-Visitor
    1-Visitor
    July 25, 2012
    Hi Jason,

    This still sounds like a deep content splitting issue, like something changed from 5.3 to 5.4. The release notes might have info.I have attached PDF on the subject from my book in hopes it might help. Note that itis based on 5.3.

    Please keep us posted on this.

    Good luck!
    Suzanne Napoleon
    www.FOSIexpert.com
    "WYSIWYG is last-century technology!"


    G
    GarethOakes16-Pearl
    16-Pearl
    July 26, 2012
    Time to try out APP ? 🙂
    N
    naglists1-Visitor
    1-Visitor
    July 26, 2012
    Do you have a <thead> in the generated table? Try removing that.

    I haven't nailed it down 100% yet, but in our migration from 5.3 to 6.0 I
    have discovered some generated tables that will not break if I use a
    <thead>.

    Technically, if I strip all the contents of the thead e-i-c, it will still
    publish correctly. It's when I start adding back the formatting it fails.
    If I'm remembering correctly, it was <font... in=" thead's=" e-i-c.=" but=" i=" could<br="/>be wrong. I think I wrote about it here ... in how much detail and when
    relative to my testing so far, I can't recall.

    E
    ebenton1-Visitor
    1-Visitor
    July 27, 2012
    If that works, you could still use < e-i-c gi="row" context="table" occur="first"> for a row with header-like formatting. You would miss the default header floating behavior for multi-page tables, but...
    A
    Anonymous
    July 27, 2012
    Wow, that was it. What the flip? That seems pretty random...

    Have you reported it to Arbortext?

    Thanks, BTW. I would have spent waaaay too much more time on this before finding that (If I did at all).
    N
    naglists1-Visitor
    1-Visitor
    July 28, 2012
    I have not reported it yet. I've been buried w/other issues ... hopefully
    those'll settle down this week and I'll be able to refine it to the point
    of case submission. I got pretty close before getting distracted.

    N
    naglists1-Visitor
    1-Visitor
    July 30, 2012
    I now have a case open against 6.0 m010 for this. Not sure what I was
    seeing earlier, but a thead in a generated tables prevents the table from
    breaking across pages: Modifying or removing the thead e-i-c has no impact.

    N
    naglists1-Visitor
    1-Visitor
    August 1, 2012
    Bizarre discovery. I was seeing inconsistent breaking / non-breaking
    behavior on these tables and independent of the thead in the generated
    tables in the FOSI and I discovered some markup that will occasionally
    cause different behavior. In the examples below, <testing_summary_anchor>
    is the tag that pulls in the generated table that will (sometimes) not
    break across pages.

    For example, this will not break:
    <h1 landscape="yes">
    <title>testsumm</title>
    <anchors>
    <testing_summary_anchor>
    <title>Testing Summary</title>
    </testing_summary_anchor>
    </anchors>
    </h1>

    This WILL break:
    <h1 landscape="yes">
    <title>testsumm</title>
    <anchors>
    <testing_summary_anchor>
    <title>Testing Summary</title>
    </testing_summary_anchor>
    </anchors>
    </h1>
    <h1>
    <title>More random stuff</title>
    <para>paragraph</para>
    <para>Lorem ipsum dolor sit amet.</para>
    <para>Etiam sollicitudin posuere nisi. Sed id dolor.</para>
    </h1>

    I think I ran a test with just a:
    <para></para>

    After the closing </anchors> and changed the break / no-break behavior.

    Now I'm suspecting keeps logic has changed somewhere in the core code. Does
    anyone remember anything about keep behavior changing anywhere in the 5.4
    or 6.0 code base?


    Show more replies
    Terms & ConditionsAccessibility statement