tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Ehrlich (JIRA) <j...@apache.org>
Subject [jira] [Updated] (TIKA-974) No longer return charset info in Metadata's CONTENT_ENCODING
Date Tue, 30 Oct 2012 18:38:12 GMT

     [ https://issues.apache.org/jira/browse/TIKA-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jörg Ehrlich updated TIKA-974:
------------------------------

    Component/s: metadata
    
> 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
>          Components: metadata
>    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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message