/**
* Copyright 2006 by Know-Center, Graz, Austria
* PDF-AS has been contracted by the E-Government Innovation Center EGIZ, a
* joint initiative of the Federal Chancellery Austria and Graz University of
* Technology.
*
* Licensed under the EUPL, Version 1.1 or - as soon they will be approved by
* the European Commission - subsequent versions of the EUPL (the "Licence");
* You may not use this work except in compliance with the Licence.
* You may obtain a copy of the Licence at:
* http://www.osor.eu/eupl/
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the Licence is distributed on an "AS IS" basis,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the Licence for the specific language governing permissions and
* limitations under the Licence.
*
* This product combines work with different licenses. See the "NOTICE" text
* file for details on the various modules and licenses.
* The "NOTICE" text file is part of the distribution. Any derivative works
* that you distribute must include a readable copy of the "NOTICE" text file.
*
* $Id: FooterParseResult.java,v 1.1 2006/08/25 17:00:59 wprinz Exp $
*/
package at.knowcenter.wag.exactparser.parsing.results;
/**
* The result of parsing a PDF footer block.
*
*
* A PDF footer block starts with the xref table followed by the trailer, the
* startxref and finally the EOF marker. Usually the footer should be at the end
* of the file. All object offsets in the footer's xref table should be before
* the footer itself. Nevertheless, there are PDF Writers (e.g. Microsoft Word)
* that put the footer at the beginning of the document so that all indirect
* objects are after the EOF marker.
*
*
* @author wprinz
*/
public class FooterParseResult extends ParseResult
{
public StartXRefParseResult sxpr = null;
public EOFParseResult eofpr = null;
public XRefSectionParseResult xpr = null;
public TrailerParseResult tpr = null;
}