[
https://issues.apache.org/jira/browse/TIKA-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343566#comment-14343566
]
Nick Burch commented on TIKA-944:
---------------------------------
With the server as-is, you can get the metadata as text, json and xmp. You can
get the text of the document as text or xhtml. You can get a list of parsers,
detectors, mime types etc
Not sure about language detection though? But I believe that we're a lot closer
to feature parity between server and cli now than we were in 2012!
> Extend tika-server API to be consistent with tika-app CLI
> ---------------------------------------------------------
>
> Key: TIKA-944
> URL: https://issues.apache.org/jira/browse/TIKA-944
> Project: Tika
> Issue Type: New Feature
> Components: server
> Affects Versions: 1.1
> Environment: Any
> Reporter: Jason Judge
> Assignee: Chris A. Mattmann
> Labels: exposed-functionality, tika-server
>
> The tika-server API (web service) provides a limited set of functionality
> compared to the tika-app command-line version. Notable things missing are:
> 1. Language recognition.
> 2. Output in various formats (JSON for metadata, XHTML for the extracted
> text).
> Those are the two main things that would be useful to me, but ideally the
> server should be able to provide all the functionality that the command-line
> app does, taking the command-line as the model to follow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
