Difference between revisions of "Plugins"
Jump to navigation
Jump to search
| (21 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
Plugins that we have, and plugins that would be nice to have for Apertium. |
|||
==Completed== |
==Completed== |
||
* OpenOffice ([http://apertium.svn.sourceforge.net/viewvc/apertium/trunk/oooapertium/ code]) |
|||
* OpenOffice |
|||
* API that mimics the API of Google Translate: implemented as part of the Google Summer of Code 2009 projects, see [[Apertium services]] |
|||
** Used in: |
|||
*** [http://translate.sourceforge.net/wiki/virtaal/index Virtaal], a Computer-Aided Translation tool mainly for gettext/po-files |
|||
*** [http://www.omegat.org/ OmegaT] (2.0 or later), a standalone Computer-Aided Translation tool |
|||
*** [http://anaphraseus.sourceforge.net/ Anaphraseus], a Computer-Aided Translation extension for OpenOffice.org/LibreOffice |
|||
*** [http://code.google.com/p/okapi/ Okapi], a framework and toolset for handling translation projects |
|||
*** … |
|||
* 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/ |
|||
* Gaupol, see [[Translating subtitles]] |
|||
* [[Apertium-OmegaT]] |
|||
==In progress== |
==In progress== |
||
* |
* X-Chat |
||
** old version by Wynand Winterbach: [[X-Chat plugin]] |
|||
** new version by [[User:Sbalbp1|Sbalbp]]: [[Plugin for XChat]] using [[Apy]] (either local or running on someone else's machine) |
|||
* Pidgin |
* Pidgin |
||
** old version: https://sourceforge.net/p/apertium/svn/HEAD/tree/trunk/apertium-tools/pidgin-apertium/ |
|||
** new version by [[User:Sbalbp1|Sbalbp]]: [[Plugin for Pidgin]] using [[Apy]] (either local or running on someone else's machine) |
|||
* Wordpress |
|||
** 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 |
|||
==Requested== |
==Requested== |
||
* A plugin for subtitle editors. |
* ''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/. |
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 [[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 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]] |
|||
| ⚫ | |||
[[Category:Tools]] |
[[Category:Tools]] |
||
| ⚫ | |||
Latest revision as of 19:20, 18 August 2014
Plugins that we have, and plugins that would be nice to have for Apertium.
Completed[edit]
- 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[edit]
- X-Chat
- old version by Wynand Winterbach: X-Chat plugin
- new version by Sbalbp: Plugin for XChat using Apy (either local or running on someone else's machine)
- Pidgin
- old version: https://sourceforge.net/p/apertium/svn/HEAD/tree/trunk/apertium-tools/pidgin-apertium/
- new version by Sbalbp: Plugin for Pidgin 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[edit]
- 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]
