[
https://issues.apache.org/jira/browse/TIKA-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17929716#comment-17929716
]
Subbu commented on TIKA-4370:
-----------------------------
_Another thought is to hardcode the text detector after MimeTypes...which I
don't like, but I'm not beyond._
[~tallison] sorry what hardcoding you mean? What I was thinking/asking is if
either the TXTParser (or anything similar that identifies the stream as SJIS at
the current place where it checks
[https://github.com/apache/tika/blob/be5003c8c55ebcc39ffecfe8e95ac5eef37b803f/tika-core/src/main/java/org/apache/tika/mime/MimeTypes.java#L293,]
and used that to conclude as SJIS and not octet stream.
Please let me know if you thinking of a better solution in tika layer.
> SJIS Encoded Files Can't be Detected
> ------------------------------------
>
> Key: TIKA-4370
> URL: https://issues.apache.org/jira/browse/TIKA-4370
> Project: Tika
> Issue Type: Bug
> Reporter: Subbu
> Priority: Major
>
> When character encoding of file is SJIS, without file name in the metadata,
> most files content-type detected as application/octet-stream. Is there zero
> support for SJIS?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
