Mailing-List: contact dev-help@tika.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tika.apache.org
Date: Tue, 8 Nov 2011 02:32:51 +0000 (UTC)
From: "Ray Gauss II (Updated) (JIRA)" <jira@apache.org>
To: dev@tika.apache.org
Message-ID: 
 <868533547.9471.1320719571929.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1486786799.9466.1320719571781.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (TIKA-775) Embed Capabilities
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ray Gauss II updated TIKA-775:
------------------------------

    Attachment: tika-parsers-embed-patch.txt
                tika-core-embed-patch.txt
    
> Embed Capabilities
> ------------------
>
>                 Key: TIKA-775
>                 URL: https://issues.apache.org/jira/browse/TIKA-775
>             Project: Tika
>          Issue Type: Improvement
>          Components: general, metadata
>    Affects Versions: 1.0
>         Environment: The default ExternalEmbedder requires that sed be installed.
>            Reporter: Ray Gauss II
>              Labels: embed, patch
>             Fix For: 1.0
>
>         Attachments: tika-core-embed-patch.txt, tika-parsers-embed-patch.txt
>
>
> This patch defines and implements the concept of embedding tika metadata into a file stream, the reverse of extraction.
> In the tika-core project an interface defining an Embedder and a generic sed ExternalEmbedder implementation meant to be extended or configured are added.  These classes are essentially a reverse flow of the existing Parser and ExternalParser classes.
> In the tika-parsers project an ExternalEmbedderTest unit test is added which uses the default ExternalEmbedder (calls sed) to embed a value placed in Metadata.DESCRIPTION then verify the operation by parsing the resulting stream.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira