[
https://issues.apache.org/jira/browse/TIKA-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-1202:
------------------------------
Attachment: TIKA-1202.patch
Would appreciate community feedback on this before I commit it (December 6?).
Is it ok to deprecate the setters and getters for the PDFParser parameters? Is
the use of a simple properties file and integration via ParseContext consistent
with design principles of Tika?
Thank you!
> Refactor PDFParser to enable easier parameter setting
> -----------------------------------------------------
>
> Key: TIKA-1202
> URL: https://issues.apache.org/jira/browse/TIKA-1202
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Affects Versions: 1.5
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Trivial
> Attachments: TIKA-1202.patch
>
>
> It would be handy to be able to set PDFParser parameters
> (extractAnnotationText, etc) in a config file and via ParseContext.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
