You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (JIRA)" <ji...@apache.org> on 2015/08/28 15:00:47 UTC
[jira] [Resolved] (TIKA-1716) Tika Server's recursive JSON output
from /rmeta different than tika-app -J output
[ https://issues.apache.org/jira/browse/TIKA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Allison resolved TIKA-1716.
-------------------------------
Resolution: Fixed
Assignee: Tim Allison (was: Chris A. Mattmann)
r1698329
Let me know if there are any surprises.
> Tika Server's recursive JSON output from /rmeta different than tika-app -J output
> ---------------------------------------------------------------------------------
>
> Key: TIKA-1716
> URL: https://issues.apache.org/jira/browse/TIKA-1716
> Project: Tika
> Issue Type: Bug
> Components: cli, server
> Reporter: Chris A. Mattmann
> Assignee: Tim Allison
> Fix For: 1.11
>
>
> Over in Tika Python, we've received a request for exposing the XHTML output that Tika provides. I noticed that in [TikaJAXRS|http://wiki.apache.org/tika/TikaJAXRS] that the JSON output from /rmeta which Tika Python uses is different from tika-app's -J command. For example, see [GrobidJournalParser|http://wiki.apache.org/tika/GrobidJournalParser]. I'm not sure they should be different. Maybe they should. But it would be nice to at least provide maybe X:TIKA:XHTMLContent or something like that in /rmeta the same way that Tika-app -J provides.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)