Difference between revisions of "Plugins"
| Line 23: | Line 23: | ||
| ==In progress== | ==In progress== | ||
| * [[X-Chat plugin]] ([ | * [[X-Chat plugin]] ([https://sourceforge.net/p/apertium/svn/HEAD/tree/trunk/apertium-tools/xchat-modules code]) | ||
| * Pidgin | * Pidgin | ||
| ** old version: https://sourceforge.net/p/apertium/svn/HEAD/tree/trunk/apertium-tools/pidgin-apertium/  | ** old version: https://sourceforge.net/p/apertium/svn/HEAD/tree/trunk/apertium-tools/pidgin-apertium/  | ||
| ** new version by Sbalbp: https://github.com/Sbalbp/Pidgin_Translator_Plugin using [[Apy]] (either local or running on someone else's machine) | ** new version by Sbalbp: https://github.com/Sbalbp/Pidgin_Translator_Plugin using [[Apy]] (either local or running on someone else's machine) | ||
| * Wordpress | * Wordpress | ||
| ** by xavi ([ | ** by xavi ([https://sourceforge.net/p/apertium/svn/HEAD/tree/trunk/apertium-tools/wp-apertium/ code], [http://xavi.infobenissa.com/bloc/2009/wp-apertium-09/?lang=en some documentation]) | ||
| ** [http://transposh.org/ Transposh plugin] can apparantly also use Apertium | ** [http://transposh.org/ Transposh plugin] can apparantly also use Apertium | ||
Revision as of 12:36, 31 May 2014
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
- 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
- …
 
 
- Used in:
- Wordpress
- Transposh supports Apertium as of 0.7.0, see http://transposh.org/version-0-7-0-the-future-of-translation-interface/
 
- Gaupol, see Translating subtitles
In progress
- X-Chat plugin (code)
- Pidgin
- old version: https://sourceforge.net/p/apertium/svn/HEAD/tree/trunk/apertium-tools/pidgin-apertium/
- new version by Sbalbp: https://github.com/Sbalbp/Pidgin_Translator_Plugin using Apy (either local or running on someone else's machine)
 
- Wordpress
- by xavi (code, some documentation)
- Transposh plugin can apparantly also use Apertium
 
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]

