[
https://issues.apache.org/jira/browse/TIKA-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224435#comment-14224435
]
Darya Arbuzova commented on TIKA-1481:
--------------------------------------
Yes, I tried that too. I got subscribed (at least I got a confirmation letter),
but still couldn't send letters nor to u...@tika.apache.org, neither even to
dev-ow...@tika.apache.org, so at that point I gave up, because I wouldn't be
able to reach out to a person that way.
This scheme is far from straight-forward... If I have troubles using Tika,
there is little possibility I can get through your e-mail subscribe thing :)
But that's just my personal feedback anyways.
> TikaJAXRS get metadata calls give different results
> ---------------------------------------------------
>
> Key: TIKA-1481
> URL: https://issues.apache.org/jira/browse/TIKA-1481
> Project: Tika
> Issue Type: Bug
> Components: server
> Affects Versions: 1.6
> Environment: Windows 8, JDK 1.8
> Reporter: Darya Arbuzova
> Priority: Minor
> Attachments: sample.csv
>
>
> Hello!
> I'm trying to use Tika in server mode.
> I downloaded tika-server-1.6.jar from http://mirror.vorboss.net/apache/tika/.
> I have tried to get file metadata in 2 different ways (as explained here:
> http://wiki.apache.org/tika/TikaJAXRS ):
> {{> curl -T sample.csv http://localhost:9998/meta --header "Content-Type:
> text/csv"}}
> {{"Content-Encoding","windows-1252"}}
> {{"Content-Type","text/plain; charset=windows-1252"}}
> and
> {{> curl -X PUT -d @sample.csv http://localhost:9998/meta --header
> "Content-Type: text/csv"}}
> {{"Content-Encoding","ISO-8859-1"}}
> {{"Content-Type","text/plain; charset=ISO-8859-1"}}
> How come they give different results in encoding if I call the same
> {{http://localhost:9998/meta}}?
> What could the other differences appear and which is the preferable way to
> get metadata?
> Many thanks!
> Best regards,
> Darya Arbuzova
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
