[
https://issues.apache.org/jira/browse/TIKA-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216351#comment-14216351
]
Tim Allison commented on TIKA-1445:
-----------------------------------
[~gagravarr], thank you for explaining the original design decision. I knew
there must be a good reason. My idea was to create one list of non-o.a.t
parsers and one list of o.a.t parsers and then prioritize the non-o.a.t. in a
joint list, but within each list, the parsers would be in the order they were
when loaded. Is it common for people to have more than the out-of-the-box
o.a.t.p.Parser services file and then maybe one user-defined one?
> 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)
