[
https://issues.apache.org/jira/browse/TIKA-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907633#action_12907633
]
Nick Burch commented on TIKA-509:
---------------------------------
Interface rename makes sense to me, I've done that
Not sure about the best way to do the strategy object, but hopefully someone
else will do! :)
Recursion was broken in ParserContainerExtractor - I've re-enabled this, but
I'm not sure if it's the best way to handle it or not? See r995438 for how I've
made it work for now.
Next up, images in word!
> Container contents extraction
> -----------------------------
>
> Key: TIKA-509
> URL: https://issues.apache.org/jira/browse/TIKA-509
> Project: Tika
> Issue Type: New Feature
> Components: parser
> Affects Versions: 0.7
> Reporter: Nick Burch
> Assignee: Nick Burch
> Priority: Minor
> Attachments: 0001-TIKA-509-Container-contents-extraction.patch
>
>
> As discussed on the mailing list:
> http://mail-archives.apache.org/mod_mbox/tika-dev/201009.mbox/%3calpine.deb.1.10.1009010000250.5...@urchin.earth.li%3e
> This service will operate in a push mode, using streaming where possible (not
> all container formats will support that). Users can control recursion, and
> will be given the chance to process each embeded file in turn. It's up to
> them if they process a file or skip it.
> It will work similar to the current Parser code, with each container having
> its own extractor in the parsers package, and the interface defined in the
> core package. There will be an Auto extractor in the core package, configured
> with a list of parser extractors just like AutoDetectParser does.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
