You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Nick Burch (JIRA)" <ji...@apache.org> on 2011/03/14 16:19:30 UTC
[jira] Created: (TIKA-615) Support TNEF (winmail.dat) via POI
Support TNEF (winmail.dat) via POI
----------------------------------
Key: TIKA-615
URL: https://issues.apache.org/jira/browse/TIKA-615
Project: Tika
Issue Type: New Feature
Components: parser
Affects Versions: 0.9
Reporter: Nick Burch
Assignee: Nick Burch
As of POI 3.8 beta 2, POI will support decoding TNEF (winamil.dat) files. (The code is in SVN, but just missed being in 3.8 beta 1)
This issue is to track adding support to Tika for getting:
* message contents (the RTF of the message body)
* message metadata (probably just the subject for now)
* attachment contents + metadata (via the usual container contents method)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TIKA-615) Support TNEF (winmail.dat) via POI
Posted by "Nick Burch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006627#comment-13006627 ]
Nick Burch commented on TIKA-615:
---------------------------------
Currently, the message body is output as an embedded entry, just like any attachments. The other option is to pass the Rtf straight to the normal Rtf parser, have that processed inline, then handle the attachments as embedded entries. Thoughts appreciated!
> Support TNEF (winmail.dat) via POI
> ----------------------------------
>
> Key: TIKA-615
> URL: https://issues.apache.org/jira/browse/TIKA-615
> Project: Tika
> Issue Type: New Feature
> Components: parser
> Affects Versions: 0.9
> Reporter: Nick Burch
> Assignee: Nick Burch
> Attachments: POI-TNEF.patch
>
>
> As of POI 3.8 beta 2, POI will support decoding TNEF (winamil.dat) files. (The code is in SVN, but just missed being in 3.8 beta 1)
> This issue is to track adding support to Tika for getting:
> * message contents (the RTF of the message body)
> * message metadata (probably just the subject for now)
> * attachment contents + metadata (via the usual container contents method)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TIKA-615) Support TNEF (winmail.dat) via POI
Posted by "Nick Burch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Burch updated TIKA-615:
----------------------------
Attachment: POI-TNEF.patch
Patch which adds TNEF parser support (+tests) using POI. The parser is modelled on the package parser, and will output embedded entries for the Rtf, and any attachments.
(Requires a recent POI svn nightly build for now, will need wait for 3.8 beta 2 before it can be committed)
> Support TNEF (winmail.dat) via POI
> ----------------------------------
>
> Key: TIKA-615
> URL: https://issues.apache.org/jira/browse/TIKA-615
> Project: Tika
> Issue Type: New Feature
> Components: parser
> Affects Versions: 0.9
> Reporter: Nick Burch
> Assignee: Nick Burch
> Attachments: POI-TNEF.patch
>
>
> As of POI 3.8 beta 2, POI will support decoding TNEF (winamil.dat) files. (The code is in SVN, but just missed being in 3.8 beta 1)
> This issue is to track adding support to Tika for getting:
> * message contents (the RTF of the message body)
> * message metadata (probably just the subject for now)
> * attachment contents + metadata (via the usual container contents method)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TIKA-615) Support TNEF (winmail.dat) via POI
Posted by "Nick Burch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018304#comment-13018304 ]
Nick Burch commented on TIKA-615:
---------------------------------
Parser added in r1091044. Currently the RTF is handled as an attachment, but we can easily change that to put the message body inline if we decide that's the best fit
> Support TNEF (winmail.dat) via POI
> ----------------------------------
>
> Key: TIKA-615
> URL: https://issues.apache.org/jira/browse/TIKA-615
> Project: Tika
> Issue Type: New Feature
> Components: parser
> Affects Versions: 0.9
> Reporter: Nick Burch
> Assignee: Nick Burch
> Fix For: 1.0
>
> Attachments: POI-TNEF.patch
>
>
> As of POI 3.8 beta 2, POI will support decoding TNEF (winamil.dat) files. (The code is in SVN, but just missed being in 3.8 beta 1)
> This issue is to track adding support to Tika for getting:
> * message contents (the RTF of the message body)
> * message metadata (probably just the subject for now)
> * attachment contents + metadata (via the usual container contents method)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TIKA-615) Support TNEF (winmail.dat) via POI
Posted by "Nick Burch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Burch resolved TIKA-615.
-----------------------------
Resolution: Fixed
Fix Version/s: 1.0
> Support TNEF (winmail.dat) via POI
> ----------------------------------
>
> Key: TIKA-615
> URL: https://issues.apache.org/jira/browse/TIKA-615
> Project: Tika
> Issue Type: New Feature
> Components: parser
> Affects Versions: 0.9
> Reporter: Nick Burch
> Assignee: Nick Burch
> Fix For: 1.0
>
> Attachments: POI-TNEF.patch
>
>
> As of POI 3.8 beta 2, POI will support decoding TNEF (winamil.dat) files. (The code is in SVN, but just missed being in 3.8 beta 1)
> This issue is to track adding support to Tika for getting:
> * message contents (the RTF of the message body)
> * message metadata (probably just the subject for now)
> * attachment contents + metadata (via the usual container contents method)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira