DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14637>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14637

fo:retrieve-marker is confused by 2-columns reports

           Summary: fo:retrieve-marker is confused by 2-columns reports
           Product: Fop
           Version: 0.20.4
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: page-master/layout
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Overview Description:
  Consider a dictionary-like report with 2 columns and a header mentioning the 
  first and the last entry for one given page.
  To obtain the first item you'd call 
  
  <fo:retrieve-marker 
    retrieve-position="first-starting-within-page" 
    retrieve-class-name="runningHeader" 
    retrieve-boundary="page"/>
    
  while to obtain the last you'd call
  
  <fo:retrieve-marker 
    retrieve-position="last-starting-within-page" 
    retrieve-class-name="runningHeader" 
    retrieve-boundary="page"/>
    
  somewhere in your header.
  The marker "runningHeader" is set as the first block when processing a given 
  dictionary entry.
  
  What happens is that the last entry mentioned in the header of a given
  page is actually the first entry of the following page.
  
  The enclosed test case shows this misbehavior.  
  This bug is always reproducible.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to