Difference between revisions of "Plugins"
| Line 21: | Line 21: | ||
* ''API that mimics the API of Google Translate. '' |
* ''API that mimics the API of Google Translate. '' |
||
If we had an API package that resembled that of Google Translate what would probably ease adoption of Apertium in a range of software. |
If we had an API package that resembled that of Google Translate what would probably ease adoption of Apertium in a range of software. This is part of the Google Summer of Code 2009 project [[Apertium going SOA]]. |
||
Revision as of 22:07, 6 August 2009
Here is a list of plugins that would be nice to have for Apertium.
Completed
- OpenOffice
In progress
- X-Chat plugin
- Pidgin
Requested
- 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. [1]. More discussion [here] and [here]
- API that mimics the API of Google Translate.
If we had an API package that resembled that of Google Translate what would probably ease adoption of Apertium in a range of software. This is part of the Google Summer of Code 2009 project Apertium going SOA.
