Talk:Become a language pair developer for Apertium

From Apertium
Revision as of 12:59, 20 March 2012 by Bech (talk | contribs) (Création discussion)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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)

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)