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

From Apertium
Jump to navigation Jump to search
(regression test)
 
(2 intermediate revisions by one other user not shown)
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.
+
# [[Installation|Install Apertium]] locally; 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.
−
# 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.
+
# 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.
  +
# Write a new rule or correct an existing rule.
 
# Compile and test again.
 
# Compile and test again.
  +
# Add a regression test to the appropriate wiki page, so, for example, if you're doing Kyrgyz->English, add a test to [[English_and_Kyrgyz/Transfer_tests]].
−
# Submit a patch to your mentor (or commit it if you have already gained developer access).
 
  +
# Submit a pull request on github and submit the url of the PR to your mentor.
   
 
[[Category:Tasks for Google Code-in|Add transfer rule]]
  
[[Category:Tasks for Google Code-in|Add transfer rule]]

Latest revision as of 21:39, 15 December 2019

  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. Add a regression test to the appropriate wiki page, so, for example, if you're doing Kyrgyz->English, add a test to English_and_Kyrgyz/Transfer_tests.
  7. Submit a pull request on github and submit the url of the PR to your mentor.
Retrieved from "https://wiki.apertium.org/w/index.php?title=Task_ideas_for_Google_Code-in/Add_transfer_rule&oldid=70935"