an unrelated (I think) float problem: repeat_title.txt "sticks" if figure occurs at top of

[naglists]

Does this sound like a bug anyone remembers? If a figure causes a new page,
the figure title continuation prints an all subsequent pages.

If I place the following:
<newpage/>
<para>page</para>

before the figure, the figure title continuation (correctly) does not print.

If I only insert the <newpage/>, the continuation still prints.

5.2 m050 composing on PE.

--
Paul Nagai

[ebenton]

We had an issue with Arbortext Editor 5.2 M050 involving “keepfloatsout” formatting. Arbortext provided patch M051 for us. The release notes for M051 say this: “SPR 1348408 — Interaction of non-repeating ?oats with keeps:floatsout no longer leads to overfull pages.”



We use Print Composer, so I don’t know if this will help your issue, but you could check it out.

[ptc-1908075]

Paul,

This sounds like a bug you should report to PTC.

Re: workarounds: Does this happen if the float is coded directly in the title eic rather than in the pseudo-element? I don't think that should matter, but maybe it's confusing the formatter about the scope.

I'm thinking you might be able to fake out the formatter by having figure output invisible gentext placement=before with leading=0 and textbrk startln=1 endln=1. Or an invisible rule placement=before.


Re: your previous email about floating, I was able to do a quick test (one of my FOSI tutorials is about
floating table titles, and the FOSI is already coded for floating). I
added indents to a couple parent elements and got the same results you did.

It seems like this oughta work. However, I don't have any examples at hand. I think tables nested like that tend to be short.

I searched the OutSpec, but I couldn't find anything that says a floatloc should inherit indents or anything else. The OutSpec says the following about floatloc:

A float location (floatloc) is similar to a layout area in the page model.

I'm not sure how Arbortext interprets that. If you ask, please let us know what you learn!

For
a workaround, I suggest saving a different value to a text variable
whenever a parent eic contains an indent. In the title eic, test the variable with
#FOSI, and code the desired indent value in the attribute rule.

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