tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Krugler (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TIKA-974) No longer return charset info in Metadata's CONTENT_ENCODING
Date Mon, 13 Aug 2012 17:36:38 GMT
Ken Krugler created TIKA-974:
--------------------------------

             Summary: No longer return charset info in Metadata's CONTENT_ENCODING
                 Key: TIKA-974
                 URL: https://issues.apache.org/jira/browse/TIKA-974
             Project: Tika
          Issue Type: Bug
    Affects Versions: 1.2
            Reporter: Ken Krugler
            Priority: Minor


As per TIKA-431, the Content-Encoding field in response headers is used to specify the compression
(gzip, deflate, etc) of the response data, not the charset (text encoding).

Currently Tika returns this from a parse request via Metadata.CONTENT_ENCODING, but that should
be deprecated and eventually phased out, e.g. in version 2.0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message