Apertium has moved from SourceForge to GitHub.
If you have any questions, please come and talk to us on #apertium on irc.freenode.net or contact the GitHub migration team.

Task ideas for Google Code-in/Add transfer rule

From Apertium
< Task ideas for Google Code-in
Revision as of 04:14, 21 October 2018 by Firespeaker (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
  1. 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₁).
  2. Install Apertium locally; install the language pair; make sure that it works.
  3. 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.).
    • In other words, run a bunch of text in L₂ through the pair and find a consistent error in the output text in L₁ that isn't grammatical.
  4. Write a new rule or correct an existing rule.
  5. Compile and test again.
  6. Submit a pull request on github and submit the url of the PR to your mentor.
Personal tools