[
https://issues.apache.org/jira/browse/TIKA-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612942#comment-17612942
]
Tim Allison commented on TIKA-3812:
-----------------------------------
The benefit of having a default tika-config.xml is that users can look at it
and make changes as necessary. With hard coded configuration, it gets a bit
more difficult.
If you need to inject the tesseract config stuff, you might consider a
tika-config template like we have in our unit tests? See, for example
{{"{ATTACHMENT_STRATEGY"}}:
https://github.com/apache/tika/blob/main/tika-integration-tests/tika-pipes-solr-integration-tests/src/test/resources/tika-config-solr-urls.xml
But I don't want to put more work on you/break what works!
> Parser Order: image get parsed by GDALParser instead of TesseractOCRParser
> --------------------------------------------------------------------------
>
> Key: TIKA-3812
> URL: https://issues.apache.org/jira/browse/TIKA-3812
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 2.4.1
> Reporter: Eugen Caruntu
> Priority: Minor
> Fix For: 2.5.0
>
> Attachments: parser-diffs.tgz
>
>
> The selected parser seems to be different in 2.4.1. For example sending an
> image (jpg/png) that was previously (2.4.0) processed by TesseractOCRParser,
> now gets parsed by GDALParser.
> Seems that when multiple parsers support same file types, the selected parser
> depends on the order in which they get loaded.
> For example the GDALParser, ImageParser and TesseractOCRParser all support
> image/jpeg, image/png, image/gif ...
> A recent change is reversing the parser order (TIKA-3750).
> Re-configuring the GDALParser by excluding the image mime types might work,
> but there could be other duplicated parsers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
