Apertium has moved from SourceForge to GitHub.
If you have any questions, please come and talk to us on #apertium on irc.freenode.net or contact the GitHub migration team.


From Apertium
Revision as of 21:20, 18 August 2014 by Unhammer (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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

[edit] Completed

  • API that mimics the API of Google Translate: implemented as part of the Google Summer of Code 2009 projects, see Apertium services
    • Used in:
      • Virtaal, a Computer-Aided Translation tool mainly for gettext/po-files
      • OmegaT (2.0 or later), a standalone Computer-Aided Translation tool
      • Anaphraseus, a Computer-Aided Translation extension for OpenOffice.org/LibreOffice
      • Okapi, a framework and toolset for handling translation projects

[edit] In progress

[edit] 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]

Personal tools