Difference between revisions of "Contributing"
Line 9: | Line 9: | ||
into a file, and sending that to the [[mailing list]]. Most likely you want to send to the one called "apertium-stuff"; [https://lists.sourceforge.net/lists/listinfo/apertium-stuff subscribe here], then attach the file and send it to apertium-stuff@lists.sourceforge.net. |
into a file, and sending that to the [[mailing list]]. Most likely you want to send to the one called "apertium-stuff"; [https://lists.sourceforge.net/lists/listinfo/apertium-stuff subscribe here], then attach the file and send it to apertium-stuff@lists.sourceforge.net. |
||
You can also send a spreadsheet file, if you prefer that. |
|||
==Getting more involved== |
==Getting more involved== |
Revision as of 12:52, 22 August 2012
There are many ways to contribute to Apertium, from sending us lists of words or phrases you find that are incorrectly translated, to getting involved in creating a new language pair or programming on tools or user interfaces.
Adding/fixing unknown words
If you have some words that are unknown in a certain language pair, you can help out by simply writing list of words and their translations, e.g.
house; noun; casa; noun f dog; noun; perro; noun m
into a file, and sending that to the mailing list. Most likely you want to send to the one called "apertium-stuff"; subscribe here, then attach the file and send it to apertium-stuff@lists.sourceforge.net.
You can also send a spreadsheet file, if you prefer that.
Getting more involved
The first thing you should do if you want to get more involved is to introduce yourself on the mailing list and hang out on our IRC channel. There is also a list of Apertium mentors.
Next you should install apertium, lttoolbox and some language pair to play around with.
If you want to create or contribute to a language pair, go through the New language pair HOWTO. This is required reading for anyone who wants to get involved with developing Apertium language pairs. Also take a look at Contributing to an existing pair, meant for those who want to contribute to existing language pairs.
Next up, the Apertium EU Workshop site is a comprehensive guide to rule based machine translation with Apertium (originally made for a four-day course on Apertium for people with little background in machine translation); print this out and read it on the bus/train/boat :)
If you're a student, Google Summer of Code (or Google Code-In for high-school students) is a good way to get involved with Apertium, and the ideas page there has lots of project tips if you're more interested in programming than linguistics/language pairs.