Difference between revisions of "Plugins"

From Apertium
Jump to navigation Jump to search
Line 11: Line 11:
 
*** [http://www.omegat.org/ OmegaT] (2.0 or later)
 
*** [http://www.omegat.org/ OmegaT] (2.0 or later)
 
*** …
 
*** …
  +
  +
* Wordpress
  +
** [http://transposh.org/ Transposh] supports Apertium as of 0.7.0, see http://transposh.org/version-0-7-0-the-future-of-translation-interface/
   
 
==In progress==
 
==In progress==

Revision as of 12:31, 14 January 2011

Plugins that we have, and plugins that would be nice to have for Apertium.


Completed

  • OpenOffice (code)
  • API that mimics the API of Google Translate: implemented as part of the Google Summer of Code 2009 projects, see Apertium services

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]