Difference between revisions of "Plugins"
| Line 17: | Line 17: | ||
It would be easy - perhaps 1-2 day's work - to add Apertium support for http://jubler.org/. See discussion and coding advice on [[http://sourceforge.net/mailarchive/forum.php?thread_name=4df21b100901221024u7d2e6198teb7026a04c13620b%40mail.gmail.com&forum_name=apertium-stuff here]] and [[http://jubler.org/smf/index.php?topic=214.0 here]]. |
It would be easy - perhaps 1-2 day's work - to add Apertium support for http://jubler.org/. See discussion and coding advice on [[http://sourceforge.net/mailarchive/forum.php?thread_name=4df21b100901221024u7d2e6198teb7026a04c13620b%40mail.gmail.com&forum_name=apertium-stuff here]] and [[http://jubler.org/smf/index.php?topic=214.0 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 tast would be to add program tools and set up scrips needed for exporting Apertium bilingual dictionaries to other platforms, i.a. omnidic, and add to f.eks. [https://apertium.svn.sourceforge.net/svnroot/apertium/trunk/apertium-mobile/] |
|
| + | * API that mimics the API of Google Translate. |
||
| + | If we had an API package that resembled that of Google Translate what would proably ease adoption of Apertium in a range of software. |
||
Revision as of 08:41, 26 March 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 tast would be to add program tools and set up scrips needed for exporting Apertium bilingual dictionaries to other platforms, i.a. omnidic, and add to f.eks. [1]
- API that mimics the API of Google Translate.
If we had an API package that resembled that of Google Translate what would proably ease adoption of Apertium in a range of software.
