Difference between revisions of "Task ideas for Google Code-in"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
An informal spot for outlining ideas for the [[Google Code-in]] (GCI) |
An informal spot for outlining ideas for the [[Google Code-in]] (GCI) |
||
# Translate the [[new language pair HOWTO]] — and in the process commit the translation system you make to the [[Incubator]] |
# '''Translation''' Translate the [[new language pair HOWTO]] — and in the process commit the translation system you make to the [[Incubator]] |
||
# Take two language pairs, use [[apertium-crossdics]] and clean up the resulting bilingual dictionary. |
# '''Development''' 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. |
# '''Evaluation''' 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. |
# '''Polishing''' 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:56, 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.
- 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.
