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

From Apertium
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).



⚫
# '''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.
# '''Code''' 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.
⚫
# '''Code''' Convert an existing resource into Apertium format, for example an analyser for Punjabi or Hindi.
⚫
# '''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.
# '''Documentation''' Document features used in language pairs but not documented in the current official documentation or wiki (for instance, cascaded interchunk transfer); integrate that into the existing "official " [[documentation]].
# '''Documentation''' Document features used in language pairs but not documented in the current official documentation or wiki (for instance, cascaded interchunk transfer); integrate that into the existing "official " [[documentation]].

⚫
# '''Training''' Writing up a simple step-by-step guide (on the wiki) for pre-university students (of varying levels of computer literacy) to install a development version of Apertium and start doing development or polishing tasks like the ones above, to become a young Apertium developer. This may reuse or link existing material.
# '''Outreach''' Writing a quick guide on 'What Apertium can and cannot do to help you with your homework'.
# '''Outreach''' Writing a quick guide on 'What Apertium can and cannot do to help you with your homework'.

⚫
# '''Quality Assurance''' Perform a human post-editting evaluation of one of our non-evaluated pairs. At least 5,000 words.
⚫
# '''Quality Assurance''' 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).

# '''Research'''

⚫
# '''Training''' Writing up a simple step-by-step guide (on the wiki) for pre-university students (of varying levels of computer literacy) to install a development version of Apertium and start doing development or polishing tasks like the ones above, to become a young Apertium developer. This may reuse or link existing material.

⚫
# '''Translation''' Translate the [[new language pair HOWTO]] — and in the process commit the translation system you make to the [[Incubator]]

# '''User interface'''




Revision as of 21:23, 18 October 2010

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


  1. Code 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.
  2. Code Convert an existing resource into Apertium format, for example an analyser for Punjabi or Hindi.


  1. Documentation Document features used in language pairs but not documented in the current official documentation or wiki (for instance, cascaded interchunk transfer); integrate that into the existing "official " documentation.
  1. Outreach Writing a quick guide on 'What Apertium can and cannot do to help you with your homework'.
  1. Quality Assurance Perform a human post-editting evaluation of one of our non-evaluated pairs. At least 5,000 words.
  2. Quality Assurance 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).
  1. Research
  1. Training Writing up a simple step-by-step guide (on the wiki) for pre-university students (of varying levels of computer literacy) to install a development version of Apertium and start doing development or polishing tasks like the ones above, to become a young Apertium developer. This may reuse or link existing material.
  1. Translation Translate the new language pair HOWTO — and in the process commit the translation system you make to the Incubator
  1. User interface
Retrieved from "https://wiki.apertium.org/w/index.php?title=Task_ideas_for_Google_Code-in&oldid=21734"