Task ideas for Google Code-in/Grow bilingual
< Task ideas for Google Code-inJump to navigation Jump to search
- 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₁), such that it has rather good monolingual dictionaries in Apertium but no reasonable bilingual dictionary (these language pairs are usually in the incubator), for instance apertium-spa-pol
- Install Apertium locally from nightlies (instructions here); clone the relevant language modules and pair from GitHub; make sure that it works. Alternatively, get Apertium VirtualBox and update, check out & compile the language pair.
- Using a large enough corpus of representative text in the source language (e.g. plain text taken from Wikipedia, newspapers, literature, etc.) detect the 200 most frequent unknown words (words in the source document which are not in the bilingual dictionaries of the language pair). See below for information about how to do this. Note: the beginner version of this task only requires 50 words.
- Add these correspondences to the bilingual dictionary (the appropriate
.dixfile) in bidix format (so that they are not unknown anymore), as well as the monolingual analysers if needed. Make sure to categorise stems correctly.
- Compile and test again
- Submit a pull request to the GitHub repositories
How to find the most frequent unknowns
<Unhammer> translate your corpus, make it one word per line, grab only the ones with * at the start, sort, count number of hits per word, sort again <Unhammer> e.g. <Unhammer> zcat corpus.txt.gz | apertium -d . ron-fra | tr ' ' '\n' | grep '^\*' | sort | uniq -c | sort -n >hitlist <asusAndrei> awesome! <Unhammer> hitlist will be unknowns sorted by frequency, but you might have to skip a couple that are "strange" or difficult to add <Unhammer> and that's ok, as long as you start from the most frequent and work your way down