User:Mlforcada/sandbox/GSoC - Revision history

Mlforcada at 13:00, 19 March 2010

2010-03-19T13:00:04Z

Mlforcada at 12:58, 19 March 2010

2010-03-19T12:58:08Z

Mlforcada at 12:47, 19 March 2010

2010-03-19T12:47:35Z

Mlforcada: Created page with '{|class="wikitable sortable" ! Task !! Difficulty !! Description !! Rationale !! Requirements !! Interested
mentors |- | '''Easy dictionary maintenance'…'

2010-03-08T10:42:08Z

Created page with '{|class="wikitable sortable" ! Task !! Difficulty !! Description !! Rationale !! Requirements !! Interested<br/>mentors |- | '''Easy dictionary maintenance'…'

New page

{|class="wikitable sortable"
! Task !! Difficulty !! Description !! Rationale !! Requirements !! Interested<br/>mentors
|-
| '''Easy dictionary maintenance''' || 2. Hard || Write code that simplifies the maintenance of the single-word part of Apertium monolingual and bilingual dictionaries. This involves building an application that parses and reads the open-class (noun, adjective, verb) single-word part of the dictionary amenable to simple, data-base-like treatment, saving the remaining (hard to treat) part of the dictionaries, allows the user to easily add words (together with their inflection paradigms) through a friendly user interface and then combines the extended single-word data with the remaining data into Apertium monolingual and bilingual dictionaries ready to be compiled. Ideas and code from [[Apertium-dixtools]] could be useful. || Apertium dictionaries are very heterogeneous, but a great part of the development of a language pair consists in adding single words to monolingual and bilingual dictionaries, and, indeed, work on this part of the dictionaries is crucial for coverage and usefulness. Currently, dictionary maintenance is difficult because it involves editing an XML file. This may be slowing down the development of many language pairs. || Knowledge of XML, XSLT and one programming language that allows XML processing and easy writing of a user interface || Mikel L. Forcada|-
|}

@@ Line 4: / Line 4: @@
 | '''Easy dictionary maintenance''' || 2.&nbsp;Hard || Write code that simplifies the maintenance of the single-word part of Apertium monolingual and bilingual dictionaries.  This involves building an application that parses and reads the open-class (noun, adjective, verb) single-word part of the dictionary amenable to simple, data-base-like treatment, saving the remaining (hard to treat) part of the dictionaries, allows the user to easily add words (together with their inflection paradigms) through a friendly user interface and then combines the extended single-word data with the remaining data into Apertium monolingual and bilingual dictionaries ready to be compiled. Ideas and code from [[Apertium-dixtools]] could be useful. || Apertium dictionaries are very heterogeneous, but a great part of the development of a language pair consists in adding single words to monolingual and bilingual dictionaries, and, indeed, work on this part of the dictionaries is crucial for coverage and usefulness. Currently, dictionary maintenance is difficult because it involves editing an XML file. This may be slowing down the development of many language pairs. || Knowledge of XML, XSLT and one programming language that allows XML processing and easy writing of a user interface ||  Mikel L. Forcada
 |-
-| '''Hybrid MT''' || 2. Hard || Building Apertium-[http://www.openmatrex.org/marclator/marclator.html Marclator] rule-based/corpus-based hybrids  || Both the rule-based machine translation system Apertium and the corpus-based machine translation system [http://www.openmatrex.org/marclator/marclator.html Marclator] do some kind of chunking of the input as well as use a relatively straightforward left-to-right machine translation strategy. This has been explored[http://www.dlsi.ua.es/~fsanchez/pub/pdf/sanchez-martinez09d.pdf before] but there are other ways to organize hybridization which should be explored (the mentors are available to discuss). Hybridization may make it easier to adapt Apertium to a particular corpus by using chunk pairs derived from it. || Knowledge of Java, C++, and scripting languages  || [[User:Mlforcada|Mlforcada]]
+| '''Hybrid MT''' || 2. Hard || Building Apertium-[http://www.openmatrex.org/marclator/marclator.html Marclator] rule-based/corpus-based hybrids  || Both the rule-based machine translation system Apertium and the corpus-based machine translation system [http://www.openmatrex.org/marclator/marclator.html Marclator] do some kind of chunking of the input as well as use a relatively straightforward left-to-right machine translation strategy. This has been explored [http://www.dlsi.ua.es/~fsanchez/pub/pdf/sanchez-martinez09d.pdf before] but there are other ways to organize hybridization which should be explored (the mentor is haopy to discuss). Hybridization may make it easier to adapt Apertium to a particular corpus by using chunk pairs derived from it. || Knowledge of Java, C++, and scripting languages, and appreciation for research-like coding projects  || [[User:Mlforcada|Mlforcada]]
 |- }

@@ Line 2: / Line 2: @@
 ! Task                       !! Difficulty !! Description !! Rationale !! Requirements !! Interested<br/>mentors
 |-
-| '''Easy dictionary maintenance''' || 2.&nbsp;Hard || Write code that simplifies the maintenance of the single-word part of Apertium monolingual and bilingual dictionaries.  This involves building an application that parses and reads the open-class (noun, adjective, verb) single-word part of the dictionary amenable to simple, data-base-like treatment, saving the remaining (hard to treat) part of the dictionaries, allows the user to easily add words (together with their inflection paradigms) through a friendly user interface and then combines the extended single-word data with the remaining data into Apertium monolingual and bilingual dictionaries ready to be compiled. Ideas and code from [[Apertium-dixtools]] could be useful. || Apertium dictionaries are very heterogeneous, but a great part of the development of a language pair consists in adding single words to monolingual and bilingual dictionaries, and, indeed, work on this part of the dictionaries is crucial for coverage and usefulness. Currently, dictionary maintenance is difficult because it involves editing an XML file. This may be slowing down the development of many language pairs. || Knowledge of XML, XSLT and one programming language that allows XML processing and easy writing of a user interface ||  Mikel L. Forcada|-
+| '''Easy dictionary maintenance''' || 2.&nbsp;Hard || Write code that simplifies the maintenance of the single-word part of Apertium monolingual and bilingual dictionaries.  This involves building an application that parses and reads the open-class (noun, adjective, verb) single-word part of the dictionary amenable to simple, data-base-like treatment, saving the remaining (hard to treat) part of the dictionaries, allows the user to easily add words (together with their inflection paradigms) through a friendly user interface and then combines the extended single-word data with the remaining data into Apertium monolingual and bilingual dictionaries ready to be compiled. Ideas and code from [[Apertium-dixtools]] could be useful. || Apertium dictionaries are very heterogeneous, but a great part of the development of a language pair consists in adding single words to monolingual and bilingual dictionaries, and, indeed, work on this part of the dictionaries is crucial for coverage and usefulness. Currently, dictionary maintenance is difficult because it involves editing an XML file. This may be slowing down the development of many language pairs. || Knowledge of XML, XSLT and one programming language that allows XML processing and easy writing of a user interface ||  Mikel L. Forcada
+|-
-| what || how hard || description|| rationale || requirements || mentors |- }
+| '''Hybrid MT''' || 2. Hard || Building Apertium-[http://www.openmatrex.org/marclator/marclator.html Marclator] rule-based/corpus-based hybrids  || Both the rule-based machine translation system Apertium and the corpus-based machine translation system [http://www.openmatrex.org/marclator/marclator.html Marclator] do some kind of chunking of the input as well as use a relatively straightforward left-to-right machine translation strategy. This has been explored[http://www.dlsi.ua.es/~fsanchez/pub/pdf/sanchez-martinez09d.pdf before] but there are other ways to organize hybridization which should be explored (the mentors are available to discuss). Hybridization may make it easier to adapt Apertium to a particular corpus by using chunk pairs derived from it. || Knowledge of Java, C++, and scripting languages  || [[User:Mlforcada|Mlforcada]]
+|- }

User:Mlforcada/sandbox/GSoC - Revision history

Mlforcada at 13:00, 19 March 2010

Mlforcada at 12:58, 19 March 2010

Mlforcada at 12:47, 19 March 2010

Mlforcada: Created page with '{|class="wikitable sortable" ! Task !! Difficulty !! Description !! Rationale !! Requirements !! Interestedmentors |- | '''Easy dictionary maintenance'…'

Mlforcada: Created page with '{|class="wikitable sortable" ! Task !! Difficulty !! Description !! Rationale !! Requirements !! Interested
mentors |- | '''Easy dictionary maintenance'…'