Difference between revisions of "Task ideas for Google Code-in/Add transfer rule"

From Apertium
Jump to navigation Jump to search
(Created page with ' # 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 lo…')
 
Line 1: Line 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₁).
 
# 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 from the Subversion repository; install the language pair; make sure that it works and/or get[http://wiki.apertium.org/wiki/Apertium_VirtualBox Apertium VirtualBox] and update, check out & compile the language pair.
 
# Install Apertium locally from the Subversion repository; install the language pair; make sure that it works and/or get[http://wiki.apertium.org/wiki/Apertium_VirtualBox Apertium VirtualBox] and update, check out & compile the language pair.
Line 6: Line 5:
 
# Submit a patch to your mentor (or commit it if you have already gained developer access).
 
# Submit a patch to your mentor (or commit it if you have already gained developer access).
   
[[Category:Task ideas for Google Code-in|Add transfer rule]]
+
[[Category:Tasks for Google Code-in|Add transfer rule]]

Revision as of 14:11, 29 October 2013

  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 from the Subversion repository; install the language pair; make sure that it works and/or getApertium VirtualBox and update, check out & compile the language pair.
  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) 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.); (4) write a new rule or correct the existing rule.
  4. Compile and test again.
  5. Submit a patch to your mentor (or commit it if you have already gained developer access).