[ 
https://issues.apache.org/jira/browse/PDFBOX-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15579528#comment-15579528
 ] 

Maruan Sahyoun edited comment on PDFBOX-3506 at 10/16/16 7:41 AM:
------------------------------------------------------------------

Yes, that's correct. The handling might be put behind a switch as it's assuming 
that we handle the processing like a 1.5+ conforming reader. Doing it like 1.4 
and earlier the XrefStm wouldn't be available and as a result the objects are 
not available.  Now for whatever reason one would like to switch between both 
version e.g. to check how a 1.4 compliant rest would be.


was (Author: msahyoun):
Yes, that's correct. The handling might be put behind a switch as it's assuming 
that we handle the processing like a 1.5+ conforming reader. Doing it like 1.4 
and earlier the XrefStm wouldn't be available and as a result the objects are 
not available.   

> Not able to read the custom metadata in trailer section
> -------------------------------------------------------
>
>                 Key: PDFBOX-3506
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-3506
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Parsing
>    Affects Versions: 2.0.3, 2.1.0
>         Environment: Windows 7, PDF version 1.5
>            Reporter: Kent Lee
>         Attachments: PDFBOX-3506.pdf, test.pdf
>
>
> When using below code does not able to retrieve custom metadata stored in 
> trailer section of pdf
> PDDocumentInformation documentInformation = document.getDocumentInformation();
>               Set<String> customMetadataKeys = 
> documentInformation.getMetadataKeys();
> Pdfbox 1.8.12 does not have this issues



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org

Reply via email to