You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Tyler Palsulich (JIRA)" <ji...@apache.org> on 2014/12/04 02:53:13 UTC

[jira] [Commented] (TIKA-1436) improvement to PDFParser

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

Tyler Palsulich commented on TIKA-1436:
---------------------------------------

Thank you for the patch! I'm sorry for the delayed response. Can you give a little bit of explanation of why you think this patch improves existing behavior? Also, there are several method/variable renames unrelated to the logical changes. Could you update the patch to remove those changes?

> improvement to PDFParser
> ------------------------
>
>                 Key: TIKA-1436
>                 URL: https://issues.apache.org/jira/browse/TIKA-1436
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 1.6
>            Reporter: Stefano Fornari
>              Labels: parser, pdf
>         Attachments: ste-20140927.patch
>
>
> with regards to the thread "[PDFParser] - read limited number of characters" on Mar 29, I would like to propose the attached patch. I noticed that in Tika 1.6 there have been some work around a better handling of the WriteLimitReachedException condition, but I believe it could be even improved. 



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