[
https://issues.apache.org/jira/browse/TIKA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720683#comment-14720683
]
Chris A. Mattmann edited comment on TIKA-1716 at 8/28/15 10:19 PM:
-------------------------------------------------------------------
Tim in [#65|http://github.com/chrismattmann/tika-python/issues/65] and in
[#67|http://github.com/chrismattmann/tika-python/pull/67] I've gone ahead and
implemented it. Works great!
was (Author: chrismattmann):
Tim in [#65|http://github.com/chrismattmann/tika-python/issues/65] and in
[#68|http://github.com/chrismattmann/tika-python/pull/68] I've gone ahead and
implemented it. Works great!
> 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)
