[
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.7
Fix Version/s: (was: 0.7)
0.8
Hey Ken, are you OK with this going into 0.8? I'm going to try and cut an 0.7
RC within the next few hours. Let me know. I saw that you mentioned having
something in Bixo for this but haven't seen a patch yet so thought it might be
OK to turn this into a 0.8 issue.
Thanks!
Cheers,
Chris
> 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, 0.7
> Reporter: Ken Krugler
> Assignee: Ken Krugler
> Fix For: 0.8
>
>
> 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.
