Plugins that we have, and plugins that would be nice to have for Apertium.
- OpenOffice (code)
- API that mimics the API of Google Translate: implemented as part of the Google Summer of Code 2009 projects, see Apertium services
- Transposh supports Apertium as of 0.7.0, see http://transposh.org/version-0-7-0-the-future-of-translation-interface/
- Gaupol, see Translating subtitles
- old version: https://sourceforge.net/p/apertium/svn/HEAD/tree/trunk/apertium-tools/pidgin-apertium/
- new version by Sbalbp: Plugin for Pidgin using Apy (either local or running on someone else's machine)
- A plugin for subtitle editors.
We have Apertium Subtitles, but instead of making our own subtitle editor it's more feasible to make an Apertium plugin for high-quality existing subtitle editors, like http://jubler.org/. It would be easy - perhaps 1—2 day's work - to add Apertium support for http://jubler.org/. See discussion and coding advice on [here] and [here].
- Automated export to mobile dictionaries.
We have Apertium-tinylex and it's fine. Yet, there are many much more developed mobile dictionary applications available, such as Omnidic - http://www.openmobiledictionary.com/ (really cool! — source at http://code.google.com/p/omnidic/source/list). The task would be to add program tools and set up scripts needed for exporting Apertium bilingual dictionaries to other platforms, i.a. omnidic, and add to f.eks. . More discussion [here] and [here]