Difference between revisions of "Plugins"

From Apertium
Jump to navigation Jump to search
Line 18: Line 18:


* ''Automated export to mobile dictionaries. ''
* ''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. [https://apertium.svn.sourceforge.net/svnroot/apertium/trunk/apertium-mobile/]
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. [https://apertium.svn.sourceforge.net/svnroot/apertium/trunk/apertium-mobile/]. More discussion [[http://sourceforge.net/mailarchive/forum.php?thread_name=20cf28cd0903242332x4f60ec3bp4007e2d49966d530%40mail.gmail.com&forum_name=apertium-stuff here]] and [[http://sourceforge.net/mailarchive/forum.php?thread_name=20cf28cd0903252243j64421109m21e3493570221801%40mail.gmail.com&forum_name=apertium-stuff here]]


* ''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.





Revision as of 08:55, 26 March 2009

Here is a list of plugins that would be nice to have for Apertium.


Completed

  • OpenOffice

In progress

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.