SetPDFXConformance and PDF Version

Google

Mailing List

Home

Forum Home

JBoss - Java Application Server

Tomcat - JSP/Servlet container

Struts - A MVC web framework

iText - An open source PDF Java Library

JDOM - JDOM XML Parser

JSP - A mailing list about Java Server Pages specification and reference

J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition

J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog

Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology

Struts & Hibernate

Subjects

•	JSP editor plugin for eclipse ?
•	org apache jasper JasperException: Unable to compile class for JSP
•	Tomcat: Connection reset by peer: socket write error
•	Cannot retrieve definition for form bean null
•	Struts Tiles Tutorial (free Struts training)
•	Where do I download Tomcat 4 0 6?
•	Data Access Object (DAO) pattern, example DAO 's
•	Where to download Tomcat v 4 1 24 from?
•	Tomcat 5 0 16 Requested resource not available
•	Subject: Servlet : Session invalidate
•	Oracle Connection Pooling in 3 2 2
•	Servlet action is currently unavailable
•	Tomcat/Struts Unicode Encoding/Decoding problems
•	Subject: Running a Simple JMS Example
•	Tomcat and webapplication specific java library path
•	Mapping in workers2 properties
•	org apache jasper JasperException
•	problem with html:text bean throwing exception
•	Cannot find message resources under key org apache struts action MESSAGE
•	Cannot find message resources under key org apache struts action MESSAGE
•	invalid direct reference problem with solution
•	Tool for jsp debug Try Sysdeo Eclipse Plugin
•	Tomcat 5 Cannot load JDBC driver class 'null ' SQL state: null
•	weblogic ejbc
•	java properties file
•	Jboss 3 2 3 Coyote Can 't re
•	Tomcat 5, Apache2 and mod jk2 integration problem
•	JBoss example problem new to J2EE
•	Value attribute of <html:checkbox
•	url string for connecting jboss to oracle
•	javax servlet ServletException: BeanUtils populate
•	5 0 18: Windows XP Pro vs Windows 2000
•	HTTP Status 404 The requested resource is not available

SetPDFXConformance and PDF Version

SetPDFXConformance and PDF Version

2007-11-14 - By -not available-

Back
Paulo,

Since you added support for PDF/A-1, one can (re-)use the method
setPDFXConformance(...) on PdfWriter to set the conformance level to
PdfWriter.PDFA1B.
Additionally, this method sets the version of the PDF to 1.3 (since the
supported standards ISO 15930-1 alias PDF/X-1a:2001 and ISO 15930-3 alias
PDF/X-3:2002 are based on PDF 1.3).

The PDF/A-1 standard, based on PDF 1.4, states that "A conforming file
may include any valid PDF 1.4 feature that is not explicitly forbidden by
this part of ..."
Shouldn't the above-mentioned method therefore leave the PDF version as
default (1.4) in case of PDF/A-1? That way you cannot create a PDF
document with version set to 1.3 and with 1.4 (and later) features. Or is
this simply the responsibility of the PDF creator to set the PDF version
to 1.4 to override this when creating PDF/A compliant documents?

I am also aware of the fact that neither the version number in the header
of a PDF file nor the value of the version key in the document catalog
dictionary shall be used in determining whether a file is in accordance
with PDF/A-1 (that is were the PDF/A Identification extension schema is
used to set version metadata). Perhaps this is the reason why you kept the
version setting to 1.3 ...

br,

-- ---- ---- ---- ---- ---- ---- ---- ---- ---- --

Inventive Designers' Email Disclaimer:

http://www.inventivedesigners.com/email-disclaimer

 Paulo,
 
 Since you added support for PDF/A-1,
one can (re-)use the method setPDFXConformance(...) on PdfWriter to set
the conformance level to PdfWriter.PDFA1B. 
 Additionally, this method sets the version
of the PDF to 1.3 (since the supported standards ISO 15930-1 alias PDF/X-1a:2001
and ISO 15930-3 alias PDF/X-3:2002 are based on PDF 1.3).
 
 The PDF/A-1 standard, based on PDF 1.4,
 states that "A conforming file
may include any valid PDF 1.4 feature that is not explicitly forbidden
by this part of ..."
 Shouldn't the above-mentioned method therefore
leave the PDF version as default (1.4) in case of PDF/A-1? That way you
cannot create a PDF document with version set to 1.3 and with 1.4 (and
later) features. Or is this simply the responsibility of the PDF creator
to set the PDF version to 1.4 to override this when creating PDF/A compliant
documents?
 
 I am also aware of the fact that neither
the version number in the header of a PDF file nor the value of the version
key in the document catalog dictionary shall be used in determining whether
a file is in accordance with PDF/A-1 (that is were the PDF/A Identification
extension schema is used to set version metadata). Perhaps this is the
reason why you kept the version setting to 1.3 ...
 
 br,<hr/>Inventive Designers' Email
Disclaimer: <a href="http://www.inventivedesigners.com/email-disclaimer"
>http://www.inventivedesigners.com/email-disclaimer</a> 

-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -----
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
iText-questions mailing list
iText-questions@(protected)
https://lists.sourceforge.net/lists/listinfo/itext-questions
Buy the iText book: http://itext.ugent.be/itext-in-action/