tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Allison (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1238) Update OutlookExtractor to handle codepage identification more rigorously
Date Mon, 20 Jul 2015 16:32:04 GMT

    [ https://issues.apache.org/jira/browse/TIKA-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633786#comment-14633786

Tim Allison commented on TIKA-1238:

That's up to the community, but I think we have another issue that will force a release within
the next few weeks.  I'm sorry I don't have a better idea.  

[~chrismattmann] et al,  what's your take on the importance of a new release after we fix

> Update OutlookExtractor to handle codepage identification more rigorously
> -------------------------------------------------------------------------
>                 Key: TIKA-1238
>                 URL: https://issues.apache.org/jira/browse/TIKA-1238
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>            Reporter: Tim Allison
>            Assignee: Tim Allison
>            Priority: Minor
>             Fix For: 1.10
> Since OutlookExtractor's codepage detection chunk was written, POI's HSMF has added more
robutst capabilities for identifying codepages in Outlook .msg files.  As a first step to
integrating those improvements, I'll copy and paste some of POI's code into OutlookExtractor.
 As a second step, I'll expose more of HSMF's capabilities within POI and then factor out
the duplicate code in Tika.

This message was sent by Atlassian JIRA

View raw message