User:Skh/Application GSoC 2010
Contents
- 1 Google Summer of Code 2010: Improving multiword support in Apertium
- 1.1 Name
- 1.2 Contact information
- 1.3 Why is it you are interested in machine translation?
- 1.4 Why is it that they are interested in the Apertium project?
- 1.5 Which of the published tasks are you interested in? What do you plan to do?
- 1.6 The problem
- 1.7 Proposed solution
- 1.8 Reasons why Google and Apertium should sponsor it
- 1.9 A description of how and who it will benefit in society
- 1.10 Work plan
- 1.11 List your skills and give evidence of your qualifications.
- 1.12 List any non-Summer-of-Code plans you have for the Summer
Google Summer of Code 2010: Improving multiword support in Apertium
This is a first draft. Comments are always welcome, but a lot is still missing.
Name
Sonja Krause-Harder
Contact information
E-mail: krauseha@gmail.com IRC: skh on freenode
Why is it you are interested in machine translation?
Why is it that they are interested in the Apertium project?
Which of the published tasks are you interested in? What do you plan to do?
The problem
Apertium already supports multiword lexical units (short: multiwords), but there are some important phenomena that can't be adequately handle yet:
- discontiguous multiwords
- separable verbs (possibly just a weird variation of the above?)
- complex multiwords
Proposed solution
- find a way to describe the various kinds of multiwords in the dictionaries
- if necessary, enhance the DTD for that
- add another step after the morphological analysis, but before the tagger, that recognizes these multiwords and either changes the result of the morphological analysis, or offers the multiword analysis as another option for the tagger
- and the other way round: in the generation phase, expand the multiwords / reorder their parts so that lt-proc -g can handle it
Reasons why Google and Apertium should sponsor it
A description of how and who it will benefit in society
Work plan
- Now: read code, work on any language pair (en-de because I know it, nl-de was suggested by Unhammer) to get acquainted with the system and the work of a language pair maintainer, really understand (as in: look at data stream) the various phases and what each binaries does
- Community bonding phase: start collecting more examples for multiwords that fit into my three categories, find out if there are more categories (not necessarily to be implemented as well, but to have the broader picture), build testcases / sample dictionaries / sample texts from the examples, ponder and discuss dictionary syntax / DTD changes (if any) on mailing list
- Week 1: Implement changes to DTD and dictionary parsing / compiling in lt-proc
- Week 2: write new module to run between lt-proc and apertium-tagger, parse compiled dictionary (?)
- Week 3:
- Week 4:
- Deliverable #1
- Week 5:
- Week 6:
- Week 7: Write detailed documentation how to use these multiwords
- Week 8:
- Deliverable #2
- Week 9:
- Week 10:
- Week 11:
- Week 12:
- Project completed
List your skills and give evidence of your qualifications.
- 7 years at SuSE Linux, Nuernberg (now Novell), without formal qualification, because I wanted to work on Linux and open source
- Software integration, RPM packaging and maintenance
- also work on "internal" (still open source) tool: http://swamp.sf.net/, designed the workflow description language and the core workflow engine
- Now 2nd year undergraduate in Linguistics (two majors actually, historical and computational linguistics).
- Most programming experience in Java, Bash. Also some C++, Perl, tcl, PHP.
- Always happy to provide references
List any non-Summer-of-Code plans you have for the Summer
University Summer term until July 24th, so for the first ~8 weeks of the program I can realistically offer 20 hours/week. After that I'll be available full-time. I am currently working 20 hours/week for a small local software company, so I am used to managing my time. If I am accepted into the GSoC program I plan to take an unpaid leave from that job for the 12 weeks of programming.
, especially employment, if you are applying for internships, and class-taking. Be specific about schedules and time commitments. we would like to be sure you have at least 30 free hours a week to develop for our project.
