[
https://issues.apache.org/jira/browse/TIKA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091161#comment-14091161
]
Hudson commented on TIKA-1385:
------------------------------
FAILURE: Integrated in tika-trunk-jdk1.7 #151 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/151/])
Update CHANGES.txt with TIKA-1385 and TIKA-1390 entries. (tpalsulich:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1616842)
* /tika/trunk/CHANGES.txt
Fix for TIKA-1385, creating an ExternalTranslator. Also creates a
MosesTranslator. (tpalsulich:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1616841)
*
/tika/trunk/tika-translate/src/main/java/org/apache/tika/language/translate/ExternalTranslator.java
*
/tika/trunk/tika-translate/src/main/java/org/apache/tika/language/translate/MosesTranslator.java
*
/tika/trunk/tika-translate/src/main/resources/org/apache/tika/language/translate/translator.moses.properties
*
/tika/trunk/tika-translate/src/test/java/org/apache/tika/language/translate/MosesTranslatorTest.java
> Create an External Translator
> -----------------------------
>
> Key: TIKA-1385
> URL: https://issues.apache.org/jira/browse/TIKA-1385
> Project: Tika
> Issue Type: Bug
> Components: translation
> Reporter: Tyler Palsulich
> Assignee: Tyler Palsulich
> Fix For: 1.7
>
>
> We should create an interface similar to ExternalParser which can use a
> command line/external Translator. This will be a good step toward machine
> translation and removing dependence on an internet-based translation API.
> I imagine this will overlap a bit with ExternalParser. So, later down the
> line, maybe we can somehow combine the two with a common interface/super
> class. For now, I am going to work on getting a Moses or Joshua translator
> (related to TIKA-1343) working.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
