Contributing - Revision history

Unhammer at 09:17, 26 May 2021

2021-05-26T09:17:51Z

Joshuajy03 at 04:31, 4 December 2019

2019-12-04T04:31:37Z

Unhammer: /* Adding/fixing unknown words */

2015-03-09T08:37:46Z

Adding/fixing unknown words

Tunedal: /* Getting more involved */

2015-02-16T07:37:11Z

Getting more involved

Firespeaker: link to IRC

2014-07-06T18:03:46Z

link to IRC

Unhammer: EU site dead :((( is there a copy somewhere?

2014-06-30T13:12:51Z

EU site dead :((( is there a copy somewhere?

Bech: Category:Documentation in English

2013-03-17T20:49:19Z

Category:Documentation in English

Unhammer at 14:21, 15 March 2013

2013-03-15T14:21:25Z

Unhammer: /* Adding/fixing unknown words */

2012-08-22T12:52:44Z

Adding/fixing unknown words

Unhammer: /* For non-programmers */

2012-08-22T12:49:47Z

For non-programmers

@@ Line 1: / Line 1: @@
 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.
-Regardless of the kind of contribution you want to do, the two things to start with are to subscribe to the mailing list [https://lists.sourceforge.net/lists/listinfo/apertium-stuff apertium-stuff], which is where most of the discussion goes on. Also, come and idle on the [[IRC|IRC channel]] <code>#apertium</code> on <code>irc.freenode.net</code>.
+Regardless of the kind of contribution you want to do, the two things to start with are to subscribe to the mailing list [https://lists.sourceforge.net/lists/listinfo/apertium-stuff apertium-stuff], which is where most of the discussion goes on. Also, come and idle on the [[IRC|IRC channel]] <code>#apertium</code> on <code>irc.oftc.net</code>.
 To decide what you want to contribute, take a look at ''[[Development]]'' and ''[[Projects]]'' for some ideas we've had around programming, extending the engine, and have a look at the ''[[Incubator]]'' if you're interested in linguistic issues. If you can't find anything that interests you or piques your interest, just send an email or ask someone on IRC and they'll be happy to help.

@@ Line 3: / Line 3: @@
 Regardless of the kind of contribution you want to do, the two things to start with are to subscribe to the mailing list [https://lists.sourceforge.net/lists/listinfo/apertium-stuff apertium-stuff], which is where most of the discussion goes on. Also, come and idle on the [[IRC|IRC channel]] <code>#apertium</code> on <code>irc.freenode.net</code>.
-To decide what you want to contribute, take a look at ''[[Development]]'' and ''[[Projects]]'' for some ideas we've had around programming, extending the engine, and have a look at the ''[[Incubator]]'' if you're interested in linguistic issues. If you can't find anything that interests you or piques your interest, just send an email or ask someone on irc and they'll be happy to help.
+To decide what you want to contribute, take a look at ''[[Development]]'' and ''[[Projects]]'' for some ideas we've had around programming, extending the engine, and have a look at the ''[[Incubator]]'' if you're interested in linguistic issues. If you can't find anything that interests you or piques your interest, just send an email or ask someone on IRC and they'll be happy to help.
 ==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.
+If you have some words that are unknown in a certain language pair, you can help out by simply writing a list of words and their translations, e.g.
 <pre>
 house; noun; casa; noun f
@@ Line 27: / Line 27: @@
 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 [[Installation|install apertium, lttoolbox and some language pair]] to play around with.
+Next, you should [[Installation|install apertium, lttoolbox, and some language pairs]] 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. You can improve the quality of the translation for an existing pair by correcting errors in the dictionaries. You will find some hints at the page [[Finding_errors_in_dictionaries]].
+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. You can improve the quality of the translation for an existing pair by correcting errors in the dictionaries. You will find some hints on the page [[Finding_errors_in_dictionaries]].
+Next up, the [https://www.abumatran.eu/wp-content/uploads/2014/12/abumatran-apertium-workshop-data-guide.pdf 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
-<!-- link dead? :(
+If you're a student, [[Google Summer of Code]] (or [https://codein.withgoogle.com/ 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.
-Next up, the [http://wiki.apertium.eu/index.php/Programme_overview 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.
 [[Category:Documentation in English]]

@@ Line 15: / Line 15: @@
 You can also send a spreadsheet file, if you prefer that.
+==Contribute language knowledge==
+The [[Indirect contribution guide]] has some tips on how to contribute your knowledge of a language to create resources that we use in Apertium, such as
+* Writing contrastive analyses
+* Cataloguing resources
+* Hand-translating text
+* Converting dictionaries
+* Contributing to related projects
 ==Getting more involved==

@@ Line 21: / Line 21: @@
 Next you should [[Installation|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.
+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. You can improve the quality of the translation for an existing pair by correcting errors in the dictionaries. You will find some hints at the page [[Finding_errors_in_dictionaries]].
 <!-- link dead? :(

@@ Line 1: / Line 1: @@
 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.
-Regardless of the kind of contribution you want to do, the two things to start with are to subscribe to the mailing list [https://lists.sourceforge.net/lists/listinfo/apertium-stuff apertium-stuff], which is where most of the discussion goes on. Also, come and idle on the IRC channel <code>#apertium</code> on <code>irc.freenode.net</code>.
+Regardless of the kind of contribution you want to do, the two things to start with are to subscribe to the mailing list [https://lists.sourceforge.net/lists/listinfo/apertium-stuff apertium-stuff], which is where most of the discussion goes on. Also, come and idle on the [[IRC|IRC channel]] <code>#apertium</code> on <code>irc.freenode.net</code>.
 To decide what you want to contribute, take a look at ''[[Development]]'' and ''[[Projects]]'' for some ideas we've had around programming, extending the engine, and have a look at the ''[[Incubator]]'' if you're interested in linguistic issues. If you can't find anything that interests you or piques your interest, just send an email or ask someone on irc and they'll be happy to help.

← Older revision		Revision as of 20:49, 17 March 2013
Line 26:		Line 26:

	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.		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.

			[[Category:Documentation in English]]