[
https://issues.apache.org/jira/browse/TIKA-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267792#comment-14267792
]
Nick Burch commented on TIKA-1445:
----------------------------------
[~lfcnassif] Longer term we'll have different config objects that let you pick
what you want - see [this
comment|https://issues.apache.org/jira/browse/TIKA-1445?focusedCommentId=14222510&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14222510]
for one possible plan
Short term, just pass in an ocr config to the parser context with an invalid
path on it, as one of the unit tests does
> Figure out how to add Image metadata extraction to Tesseract parser
> -------------------------------------------------------------------
>
> Key: TIKA-1445
> URL: https://issues.apache.org/jira/browse/TIKA-1445
> Project: Tika
> Issue Type: Bug
> Components: parser
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 1.8
>
> Attachments: 000003.doc, TIKA-1445.Mattmann.101214.patch.txt,
> TIKA-1445.Palsulich.102614.patch, TIKA-1445_20150106_tallison.patch,
> TIKA-1445_tallison_20141027.patch.txt, TIKA-1445_tallison_v2_20141027.patch,
> TIKA-1445_tallison_v3_20141027.patch
>
>
> Now that Tesseract is the default image parser in Tika for many image types,
> consider how to add back in the metadata extraction capabilities by the other
> Image parsers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
