Difference between revisions of "Task ideas for Google Code-in"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
# '''Evaluation''' Perform a human post-editting evaluation of one of our non-evaluated pairs. At least 5,000 words. |
# '''Evaluation''' Perform a human post-editting evaluation of one of our non-evaluated pairs. At least 5,000 words. |
||
# '''Polishing''' Make some concrete improvements in a language pair. This might be disambiguation, transfer or vocabulary (in particular, minor-major language pairs would appreciate input: Welsh-English, Basque-Spanish, Breton-French). |
# '''Polishing''' Make some concrete improvements in a language pair. This might be disambiguation, transfer or vocabulary (in particular, minor-major language pairs would appreciate input: Welsh-English, Basque-Spanish, Breton-French). |
||
# '''Conversion''' Convert an existing resource into Apertium format, for example an analyser for Punjabi or Hindi. |
|||
[[Category:Google Code-in]] |
[[Category:Google Code-in]] |
||
Revision as of 21:00, 18 October 2010
An informal spot for outlining ideas for the Google Code-in (GCI)
- Translation Translate the new language pair HOWTO — and in the process commit the translation system you make to the Incubator
- Development Take two language pairs, use apertium-crossdics and clean up the resulting bilingual dictionary. For instance, build Occitan-French from Occitan-Catalan and Catalan-French.
- Evaluation Perform a human post-editting evaluation of one of our non-evaluated pairs. At least 5,000 words.
- Polishing Make some concrete improvements in a language pair. This might be disambiguation, transfer or vocabulary (in particular, minor-major language pairs would appreciate input: Welsh-English, Basque-Spanish, Breton-French).
- Conversion Convert an existing resource into Apertium format, for example an analyser for Punjabi or Hindi.
