Difference between revisions of "Apertium services"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
==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, in particular using [[NUL flushing]]. |
||
* [[D-Bus service for Apertium]] |
* [[D-Bus service for Apertium]] |
||
* [[JSON-RPC Apertium services]] (eh?) |
* [[JSON-RPC Apertium services]] (eh?) |
||
Revision as of 17:44, 15 January 2014
There are two main Apertium service implementations:
apertium-service, described at Apertium-service; its development was documented here: Apertium going SOA
and
ScaleMT, see ScaleMT
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)
