Difference between revisions of "Apertium services"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
There are |
There are three main Apertium service implementations: |
||
* <code>apertium-service</code>, |
* <code>apertium-service</code>, see [[Apertium-service]] (its development was documented here: [[Apertium going SOA]]) |
||
and |
|||
* <code>ScaleMT</code>, see [[ScaleMT]] |
* <code>ScaleMT</code>, see [[ScaleMT]] |
||
* <code>apertium-apy<code>, see [[apy]], a Python 3 tornado http server |
|||
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. |
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. |
||
Revision as of 19:51, 15 January 2014
There are three main Apertium service implementations:
apertium-service, see Apertium-service (its development was documented here: Apertium going SOA)
ScaleMT, see ScaleMT
apertium-apy, see apy, a Python 3 tornado http server
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 Virtaal, Okapi, OmegaT, begiak, …
See also
- Daemon for code examples on how to run an apertium language pair as a daemon, in particular using NUL flushing.
- D-Bus service for Apertium
- JSON-RPC Apertium services (eh?)
- lttoolbox API (for calling a local lttoolbox from C++/Python)
