Task ideas for Google Code-in/Add transfer rule
< Task ideas for Google Code-in
Jump to navigation
Jump to search
Revision as of 19:12, 30 October 2017 by Firespeaker (talk | contribs)
- select a language pair, ideally such that the source language is a language you know (L₂) and the target language a language you use every day (L₁).
- Install Apertium locally; install the language pair; make sure that it works.
- and/or get Apertium VirtualBox and update, check out & compile the language pair.
- Using a large enough corpus of the source language (e.g. plain text taken from Wikipedia), detect one structural transfer rule (.t1x, .t2x, .t3x) that is wrong or missing (local agreement, gender, number, etc. is inadequate, local word order in a phrase is inadequate, there is a word too much or a word missing, etc.).
- Write a new rule or correct an existing rule.
- Compile and test again.
- Submit a patch to your mentor (or commit it if you have already gained developer access).
