H
 
I am using APACHE FOP and iText for rendering a PDFA/1b complaint PDF from
my application, and currently facing an issue. It seems like my PDF is not
PDFA complaint, though it shows it is in some online validations.
I have attached a modal PDF and it does not complaint to* PDFA/1b* but it
shows as PDFA complaint in PDF relader.

The error stack from the online tool
(http://www.validatepdfa.com/online.htm) is as follows.
http://apache-fop.1065347.n5.nabble.com/file/n36629/1344841243717_v1.4.pdf
1344841243717_v1.4.pdf 

<metadata>
  <problem severity="error" objectID="25" clause="6.7"
standard="pdfa">*Language qualifier missing for property
'dc:description'*</problem>
  <problem severity="error" objectID="25" clause="6.7"
standard="pdfa">*Language qualifier missing for property
'dc:title'*</problem>
  <problem severity="error" objectID="25" clause="TN0003"
standard="pdfa">*Property 'pdf:keywords' shall use a custom embedded
schema*</problem>
  <problem severity="error" objectID="25" clause="6.7.3"
standard="pdfa">*Document information entry 'Keywords' not synchronized with
metadata property 'pdf:Keywords'*</problem>
</metadata>
  
<fonts>
  <problem severity="error" objectID="6" clause="6.3.5"
standard="pdfa">*Missing or incorrect CIDSet for CIDFont subset*</problem>
  <problem severity="error" objectID="18" clause="6.3.5"
standard="pdfa">*Missing or incorrect CIDSet for CIDFont subset*</problem>
</fonts>

For the PDF keyword property, we set only one value as the keyword but
automatically "Subject" is appended to the keyword. This makes the Keyword
property and the metadata not equal and will make the PDF not PDFA
complaint.
Can you let me know whether I am correct here? Or any other suggestion?

A sample PDFA file as attached herewith.
Any reply will be highly appreciated.
Thank you.
-Manulak 



--
View this message in context: 
http://apache-fop.1065347.n5.nabble.com/Property-pdf-keywords-shall-use-a-custom-embedded-schema-in-PDFA-tp36629.html
Sent from the FOP - Dev mailing list archive at Nabble.com.

Reply via email to