You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/07/25 17:50:38 UTC

[jira] [Commented] (TIKA-1376) Improve embedded file name extraction in PDFParser

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

Hudson commented on TIKA-1376:
------------------------------

SUCCESS: Integrated in tika-trunk-jdk1.7 #119 (See [https://builds.apache.org/job/tika-trunk-jdk1.7/119/])
TIKA-1376: improve embedded file name extraction in PDFParser (tallison: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1613444)
* /tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/pdf/PDF2XHTML.java
* /tika/trunk/tika-parsers/src/test/java/org/apache/tika/parser/pdf/PDFParserTest.java
* /tika/trunk/tika-parsers/src/test/resources/test-documents/testPDF_multiFormatEmbFiles.pdf


> Improve embedded file name extraction in PDFParser
> --------------------------------------------------
>
>                 Key: TIKA-1376
>                 URL: https://issues.apache.org/jira/browse/TIKA-1376
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>            Reporter: Tim Allison
>            Assignee: Tim Allison
>            Priority: Trivial
>             Fix For: 1.6
>
>
> When we extract embedded files from PDFs, we are currently using the key in the PDEmbeddedFilesNameTreeNode as the file name that we store as the value of Metadata.RESOURCE_NAME_KEY in the embedded document's  metadata.
> I think we should try to get the file name from PDComplexFileSpecification's getFilename() first.  If that is null, then we should fall back to the key value.



--
This message was sent by Atlassian JIRA
(v6.2#6252)