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.

Talk:Become a language pair developer for Apertium

From Apertium
Jump to: navigation, search

[edit] Method 1, Step 2 and Final Step : Compilation & Installation

The same things (how to compile and to install) are said at the end of Step 2: Get Apertium, lttoolbox, & Your Language Pair(s) chapter and in the specific chapter Final Step: Compilation & Installation.

I think these information should be only into the specific chapter. Bech 12:59, 20 March 2012 (UTC)

[edit] Getting a language pair from a Ubuntu/Debian repository to modify it

No problem if somebody gets Apertium and language pairs from a Ubuntu/Debian repository of anywhere else out of Apertium repository on Sourceforce, it it is just to use them for translations.

But this page has been written to help changing things in dictionaries. So the risk is to use a version of the language pair older than the last one.

I think Method 2: PACKAGE MANAGER could be used to get lttoolbox but should not (must not without precaution) be used to get a langage pair if you intend to modify it. This problem is noticed at the end of the page (Show it to the World) but it would be better to speak of it a bit earlier !

If you look at the List of language pairs page, you will see that released pairs (in Trunk) are more often updated than others at Staging or Nursery level. So you may be really lucky if you succeed to get the last version of a language pair out of Sourceforge repository. Another thing is : using the official Apertium repository gives you access to every language pairs (from Incubator to Trunk) when another repository will only know released pairs.

All these problems should be noticed in the chapter Method 2: PACKAGE MANAGER Bech 12:59, 20 March 2012 (UTC)

[edit] Reply to Suggestions

I'm sure that I should have mentioned this on the page, but anyone is welcome to improve or revise my work once I have finished writing it. Without the help of the Apertium community, this and many other articles are bound to become outdated or lack neccesary elements such as the ones listed. I unfortunately, don't have the time or experience to make my pages as detailed as needed for more advanced users than myself. I would honestly appreciate revisions or additions that my work has created the foundation for and I believe everyone can benefit from this.

It will likely be during this coming Google Code-In that I either create more articles or revise the existing ones. Until then I won't have much time for anything more than doing small revisions.

Thanks again for anyone willing to contribute.

Personal tools