Difference between revisions of "Ideas for Google Summer of Code/Adopt a language pair"

From Apertium
Jump to navigation Jump to search
Line 1: Line 1:
This project will involve writing linguistic data, including morphological rules and transfer rules — which are specified in a declarative language. A good intro would be to look through [[Apertium New Language Pair HOWTO]]. If the pair has OK dictionaries but a bad tagger (disambiguator), a GsoC project might involve writing a good [[Constraint Grammar]] for the pair (although this would likely require more knowledge of and interest in linguistics).
+
This project will involve writing linguistic data, including morphological rules and transfer rules — which are specified in a declarative language. A good intro would be to look through [[Apertium New Language Pair HOWTO]], see also [[Contributing to an existing pair]]. If the pair has OK dictionaries but a bad tagger (disambiguator), a GsoC project might involve writing a good [[Constraint Grammar]] for the pair (although this would likely require more knowledge of and interest in linguistics).
   
 
Here are a few links to pages of pairs which are up for adoption:
 
Here are a few links to pages of pairs which are up for adoption:

Revision as of 05:56, 27 March 2011

This project will involve writing linguistic data, including morphological rules and transfer rules — which are specified in a declarative language. A good intro would be to look through Apertium New Language Pair HOWTO, see also Contributing to an existing pair. If the pair has OK dictionaries but a bad tagger (disambiguator), a GsoC project might involve writing a good Constraint Grammar for the pair (although this would likely require more knowledge of and interest in linguistics).

Here are a few links to pages of pairs which are up for adoption:

Closely related:

Not closely related:

If you find a pair in the Incubator in SVN, feel free to write up its status on a page on the Wiki and add it here.

And pairs which were adopted in past years: