OK. Thanks for getting back to me. I'll probably roll back to 20.3 for
now as many of our reports use running headers (by page).
-Lou
"J.Pietschmann" <[EMAIL PROTECTED]> on 04/18/2003 08:12:40
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: "Illegal 'retrieve-boundary' value" error after upgrading to
0.20.5rc2
[EMAIL PROTECTED] wrote:
> They all look fine in the FO, i.e.:
>
> <fo:block>Manifest ID: <fo:retrieve-marker retrieve-position
> ="first-including-carryover" retrieve-boundary="page" retrieve-class-name
> ="marker__manifest_id"/>
Ouch, I misread the message. You triggered a bug in 0.20.5rc2. This
happens if retrieve-boundary="page" but no matching marker could
be retrieved from the page. Remember that "first-including-carryover"
does not work porperly.
For example for
<fo:block>
<fo:marker marker-class="A">...</fo:marker>
foo
<fo:block break-after="page"/>
bar
</fo:block>
on the page wit "bar" on it the "A" marker should be retrieved
but this doesn't work.
The problem with the exception is fixed, but you'll still get
nothing instead of the desired marker. There is no good workaround
for this problem. You can try to use retrieve-boundary="document".
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
