[
https://issues.apache.org/jira/browse/TIKA-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217965#comment-14217965
]
Tim Allison commented on TIKA-1445:
-----------------------------------
How about using the order of parsers as specified in TikaConfig? That should
accommodate 6 class files in different jars, no?
Via TikaConfig, we could also specify the which subclass of a default composite
parser to use. I now see at least three use cases:
1) Tika classic: pick the first parser that applies and hope that it is the one
you meant, ignore the others. :)
2) The use case we've been discussing, where each parser is additive.
3) A BackOffOnExceptionParser (TIKA-1483 got me thinking about this)
> 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: TIKA-1445.Mattmann.101214.patch.txt,
> TIKA-1445.Palsulich.102614.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)
