Difference between revisions of "Apertium services"
Jump to navigation
Jump to search
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
For using Apertium as a service you should use: |
|||
| ⚫ | |||
There are also two legacy Apertium service implementations both of which need maintenance: |
|||
* <code>apertium-service</code>, see [[Apertium-service]], a multithreaded C++ XML-RPC/REST/SOAP server, using apertium as a library |
* <code>apertium-service</code>, see [[Apertium-service]], a multithreaded C++ XML-RPC/REST/SOAP server, using apertium as a library |
||
* <code>ScaleMT</code>, see [[ScaleMT]], a multiprocess Java XML-RPC/REST server, starting apertium language pairs as new processes |
* <code>ScaleMT</code>, see [[ScaleMT]], a multiprocess Java XML-RPC/REST server, starting apertium language pairs as new processes |
||
If you want to run a translation server yourself, just [[Installation|install some language pairs]] and run [[Apy]], it's pretty simple. Or, if you're lazy, you can use our server, more info at [[Apy]]. |
|||
| ⚫ | |||
You can download the source code of these services and install any of them on your own server, or use the [[Apertium web service]], which is based on [[ScaleMT]] and is installed on our servers. |
|||
Applications which use the Apertium service include [http://translate.sourceforge.net/wiki/virtaal/index Virtaal], [http://code.google.com/p/okapi/ Okapi], [http://www.omegat.org/ OmegaT], [[begiak]], … |
Applications which use the Apertium service include [http://translate.sourceforge.net/wiki/virtaal/index Virtaal], [http://code.google.com/p/okapi/ Okapi], [http://www.omegat.org/ OmegaT], [[begiak]], [https://www.mediawiki.org/wiki/Content_translation/FAQ Wikipedia's Content Translation] (running on their own servers) … |
||
==See also== |
==See also== |
||
* [[Daemon]] for code examples on how to run an apertium language pair as a daemon, |
* [[Daemon]] for code examples on how to run an apertium language pair as a daemon, e.g. using [[NUL flushing]]. |
||
* [[D-Bus service for Apertium]] |
* [[D-Bus service for Apertium]] |
||
* [[JSON-RPC Apertium services]] (eh?) |
* [[JSON-RPC Apertium services]] (eh?) |
||
Latest revision as of 16:41, 13 February 2018
For using Apertium as a service you should use:
apertium-apy, see Apy, a multiprocess Python 3 tornado http server, starting apertium language pairs as new processes
There are also two legacy Apertium service implementations both of which need maintenance:
apertium-service, see Apertium-service, a multithreaded C++ XML-RPC/REST/SOAP server, using apertium as a libraryScaleMT, see ScaleMT, a multiprocess Java XML-RPC/REST server, starting apertium language pairs as new processes
If you want to run a translation server yourself, just install some language pairs and run Apy, it's pretty simple. Or, if you're lazy, you can use our server, more info at Apy.
Applications which use the Apertium service include Virtaal, Okapi, OmegaT, begiak, Wikipedia's Content Translation (running on their own servers) …
See also[edit]
- Daemon for code examples on how to run an apertium language pair as a daemon, e.g. using NUL flushing.
- D-Bus service for Apertium
- JSON-RPC Apertium services (eh?)
- lttoolbox API (for calling a local lttoolbox from C++/Python)
