[
https://issues.apache.org/jira/browse/TIKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888194#comment-15888194
]
Tim Allison commented on TIKA-2273:
-----------------------------------
All appears to work in 1.x. I'm still having problems loading any encoding
detector in the overall bundle in 2.x
This is for a separate issue, but I wanted to document: I also found that we
need to have some method of ordering SPI encoding detectors between packages
e.g. text vs. web. In Tika 1.x, we have one service provider/location for
encoding detection, and we load them in in the order they appear in that one
file. However, if someone adds their own or in 2.x where we have a service
file in text and one in web, the order is not guaranteed. For the parsers, we
rely on sorting by the parsers' class name. Should we do this for
EncodingDetectors or remove them from SPI and require configuration, or perhaps
centralization in tika-core???
> Enable configuration of EncodingDetectors via TikaConfig
> --------------------------------------------------------
>
> Key: TIKA-2273
> URL: https://issues.apache.org/jira/browse/TIKA-2273
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Minor
> Attachments: TIKA_2273_first_draft.patch
>
>
> It would be nice to allow easier configuration of encoding detectors. It
> should be straightforward to follow the example of detectors...(famous last
> words).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
