You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Ken Krugler (JIRA)" <ji...@apache.org> on 2010/11/05 21:14:47 UTC
[jira] Created: (TIKA-544) AutoDetectParser ignores charset in
Content-Type metadata
AutoDetectParser ignores charset in Content-Type metadata
---------------------------------------------------------
Key: TIKA-544
URL: https://issues.apache.org/jira/browse/TIKA-544
Project: Tika
Issue Type: Bug
Affects Versions: 0.7
Reporter: Ken Krugler
Assignee: Ken Krugler
Fix For: 0.8
AutoDetectParser.parse() does this:
MediaType type = detector.detect(stream, metadata);
metadata.set(Metadata.CONTENT_TYPE, type.toString());
So the charset in the Metadata.CONTENT_TYPE is blown away. On entry to the parser, it should pick this apart and set the Metadata.CONTENT_ENCODING if it's null, and the content-type has charset info.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TIKA-544) AutoDetectParser ignores charset in
Content-Type metadata
Posted by "Ken Krugler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ken Krugler closed TIKA-544.
----------------------------
Resolution: Invalid
After researching this in more depth, the real issue is that the HtmlParser and TXTParser need to use a different algorithm for deciding on the charset.
This issue is already being tracked by TIKA-539
> AutoDetectParser ignores charset in Content-Type metadata
> ---------------------------------------------------------
>
> Key: TIKA-544
> URL: https://issues.apache.org/jira/browse/TIKA-544
> Project: Tika
> Issue Type: Bug
> Affects Versions: 0.7
> Reporter: Ken Krugler
> Assignee: Ken Krugler
> Fix For: 0.8
>
>
> AutoDetectParser.parse() does this:
> MediaType type = detector.detect(stream, metadata);
> metadata.set(Metadata.CONTENT_TYPE, type.toString());
> So the charset in the Metadata.CONTENT_TYPE is blown away. On entry to the parser, it should pick this apart and set the Metadata.CONTENT_ENCODING if it's null, and the content-type has charset info.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.