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

From Apertium
Jump to navigation Jump to search
Line 11: Line 11:
 
** If there is no translation, translate it into the languages of your language pair first.
 
** If there is no translation, translate it into the languages of your language pair first.
 
* Upload your work to Apertium [[SVN]].
 
* Upload your work to Apertium [[SVN]].
  +
  +
The URL to your coding challenge work should be included in your application.
   
 
==Previous GSOC projects==
 
==Previous GSOC projects==

Revision as of 10:55, 16 February 2012

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.

Coding challenge

The coding challenge for this task is to ...

  • Install Apertium (see Minimal installation from SVN)
  • Go through the HOWTO
  • Go through the MT course here (или здесь)
  • Write a translator that translates as much of this story as possible. Other translations can be found here.
    • If there is no translation, translate it into the languages of your language pair first.
  • Upload your work to Apertium SVN.

The URL to your coding challenge work should be included in your application.

Previous GSOC projects

And pairs which were adopted in past years:

See also