tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TIKA-359) Calls to Charset.isSupported() will throw exceptions for invalid charset names
Date Wed, 20 Jan 2010 02:05:54 GMT

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

Chris A. Mattmann updated TIKA-359:
-----------------------------------

    Affects Version/s: 0.6
        Fix Version/s:     (was: 0.6)
                       0.7

- if there are no objections, I'd like to push this to 0.7 since I (for really real this time)
am cutting an RC of Tika 0.6 tonight...

> Calls to Charset.isSupported() will throw exceptions for invalid charset names
> ------------------------------------------------------------------------------
>
>                 Key: TIKA-359
>                 URL: https://issues.apache.org/jira/browse/TIKA-359
>             Project: Tika
>          Issue Type: Bug
>    Affects Versions: 0.5, 0.6
>            Reporter: Ken Krugler
>            Assignee: Ken Krugler
>             Fix For: 0.7
>
>
> The HtmlParser and TXTParser code currently call Charset.isSupported() to determine if
charset hint info (from meta tags or incoming metadata).
> But this method throws IllegalCharsetNameException for unknown (versus unsupported) encoding
names, which kills the parsing process.
> What's needed is a wrapper that catches this exception and returns false.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message