Difference between revisions of "Task ideas for Google Code-in"

From Apertium
Jump to navigation Jump to search
Line 4: Line 4:
 
# Take two language pairs, use [[apertium-crossdics]] and clean up the resulting bilingual dictionary.
 
# Take two language pairs, use [[apertium-crossdics]] and clean up the resulting bilingual dictionary.
 
# Perform a human post-editting evaluation of one of our non-evaluated pairs. At least 5,000 words.
 
# Perform a human post-editting evaluation of one of our non-evaluated pairs. At least 5,000 words.
  +
# Make some concrete improvements in a language pair. This might be disambiguation, transfer or vocabulary.
 
   
 
[[Category:Google Code-in]]
 
[[Category:Google Code-in]]

Revision as of 20:55, 18 October 2010

An informal spot for outlining ideas for the Google Code-in (GCI)

  1. Translate the new language pair HOWTO — and in the process commit the translation system you make to the Incubator
  2. Take two language pairs, use apertium-crossdics and clean up the resulting bilingual dictionary.
  3. Perform a human post-editting evaluation of one of our non-evaluated pairs. At least 5,000 words.
  4. Make some concrete improvements in a language pair. This might be disambiguation, transfer or vocabulary.