https://wiki.apertium.org/w/api.php?action=feedcontributions&user=Sortiz&feedformat=atomApertium - User contributions [en]2024-03-29T15:37:23ZUser contributionsMediaWiki 1.34.1https://wiki.apertium.org/w/index.php?title=Ideas_for_Google_Summer_of_Code&diff=32435Ideas for Google Summer of Code2012-02-28T14:44:26Z<p>Sortiz: /* List */</p>
<hr />
<div>{{TOCD}}<br />
This is the ideas page for [[Google Summer of Code]], here you can find ideas on interesting projects that would make Apertium more useful for people and improve or expand our functionality. If you have an idea please add it below, if you think you could mentor someone in a particular area, add your name to "Interested mentors" using <nowiki>~~~</nowiki> <br />
<br />
The page is intended as an overview of the kind of projects we have in mind. If one of them particularly piques your interest, please come and discuss with us on <code>#apertium</code> on <code>irc.freenode.net</code>, mail the [[Contact|mailing list]], or draw attention to yourself in some other way. <br />
<br />
Note that, if you have an idea that isn't mentioned here, we would be very interested to hear about it.<br />
<br />
Here are some more things you could look at:<br />
<br />
* [[Top tips for GSOC applications]] <br />
* Get in contact with one of our long-serving [[List of Apertium mentors|mentors]] &mdash; they are nice, honest!<br />
* Pages in the [[:Category:Development|development category]]<br />
* Resources that could be converted or expanded in the [[incubator]]. Consider doing or improving a language pair (see [[incubator]] and [[nursery]] for pairs that need work)<br />
* Unhammer's [[User:Unhammer/wishlist|wishlist]]<br />
* The [http://bugs.apertium.org/cgi-bin/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= open bugs] page on Bugzilla<br />
<br />
<!--<br />
See the list sorted by: {{comment|Do we need this? - [[User:Francis Tyers|Francis Tyers]]}}<br />
<br />
* [[/Difficulty|difficulty level]], <br />
* [[/Thematic|theme]]<br />
--><br />
==List==<br />
<br />
{|class="wikitable"<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Adopt a language pair'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
|XML, a scripting language (Python, Perl), good knowledge of the language pair adopted. || Take on an orphaned language pair, and bring it up to release quality results. What this quality will be will depend on the language pair adopted, and will need to be discussed with the prospective mentor. This will involve writing linguistic data (including morphological rules and transfer rules &mdash; which are specified in a declarative language &mdash; and possibly [[Constraint Grammar]] rules if that is relevant) || Apertium has a few pairs of languages (e.g. mt-he, ga-gd, ur-hi, id-ms, pl-cs, etc...) that are orphaned, they don't have active maintainers. A lot of these pairs have a lot of work already put in, just need another few months to get them to release quality. See also [[Incubator]] || [[User:Francis Tyers|Francis Tyers]], [[User:Jimregan|Jimregan]], [[User:Kevin Scannell|Kevin&nbsp;Scannell]], [[User:Trondtr|Trondtr]], [[User:Unhammer|Unhammer]], [[User:Darthxaher|Darthxaher]], [[User:Firespeaker|Firespeaker]], [[User:Hectoralos|Hectoralos]]<br />
|-<br />
!style="background-color: #cdcdef"| 4.&nbsp;Entry&nbsp;level ||colspan=2| || [[/Adopt a language pair|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Discontiguous multiwords'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
|C++, Knowledge of FSTs || The task will be to develop, or adapt a module to deal with these kind of contiguous multiword expressions, for example, taking 'liggja ekki fyrir' and reordering it as 'liggja# fyrir ekki'. || In many languages, such as English, Norwegian and Icelandic, there are discontiguous multiwords, e.g. phrasal verbs, that we cannot easily support. For example 'liggja ekki fyrir' in Icelandic should be translated in English as 'to be not clear', but we cannot have 'liggja fyrir' as a traditional multiword because of the extra 'adverb', or it could even be a whole NP. || [[User:Francis Tyers|Francis Tyers]], [[User:Jimregan|Jimregan]]<br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/Discontiguous multiwords|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Flag diacritics in lttoolbox'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C++ or Java, XML, Knowledge of FSTs || Adapt [[lttoolbox]] to elegantly use flag diacritics. Flag diacritics are a way of avoiding transducer size blow-up by discarding impossible paths at runtime as opposed to compile time. || This will involve designing some changes to our XML dictionary format (see [[lttoolbox]], and implementing the associated changes in the FST compiling processing code. The reason behind this is that many languages have prefix inflection, and we cannot currently deal with this without either making paradigms useless, or overanalysing (e.g. returning analyses where none exist). Flag diacritics (or constraints) would allow us to restrict overanalysis without blowing up the size of our dictionaries. || [[User:Francis Tyers|Francis Tyers]]&nbsp;(C++), [[User:Jacob Nordfalk|Jacob Nordfalk]] (Java)<br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Flag diacritics in lttoolbox|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Rule-based finite-state disambiguation'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| XML, C++ || Currently Apertium only has a bigram/trigram part-of-speech tagger. The objective of this task would be to implement a disambiguation framework for Apertium that can be expressed as a finite-state transducer. It might be a good idea to express this as constraint rules, in a novel XML-based file format. || For some languages, bigram/trigram POS disambiguation really doesn't work, especially when you want to disambiguate morphology (e.g. number, case) along with part-of-speech. So far we've been using [[constraint grammar]] for some of these languages. But although Constraint Grammar is great and powerful, it is also pretty slow. It would be a good idea to look at LanguageTool, and IceParser and Apertium's own [[apertium-lex-tools]] to get ideas on how this might be accomplished. || [[User:Francis Tyers|Francis Tyers]] <br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Rule-based finite-state disambiguation|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Complex multiwords'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Java or C++, XML, Knowledge of FSTs || Write a bidirectional module for specifying complex multiword units, for example ''dirección general'' and ''zračna luka''. See ''[[Multiwords]]'' for more information. || Although in the Romance languages it is not a big problem, as soon as you start to get to languages with cases (e.g. Serbo-Croatian, Slovenian, German, etc.) the problem comes that you can't define a multiword of <code>adj nom</code> because the adjective has a lot of inflection. || [[User:Jimregan|Jimregan]]<br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Complex multiwords|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Optimise the VM for transfer'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Python, C++, XML, code optimisation, JIT techniques, etc. || The current VM for the transfer architecture of Apertium is up to five times slower than the XML tree-walking implementation. The job of this task is to optimise the C++ code to make it faster than XML tree-walking. || The rationale behind this is that XML tree-walking is quite slow and CPU intensive. In modern (3 or more stage) pairs, transfer takes up most of the CPU. There are other options, like [[Bytecode for transfer]], but we would like something that does not require external libraries and is adapted specifically for Apertium. || [[User:Sortiz|Sortiz]]<br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/Optimise the VM for transfer|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Accent and diacritic restoration'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C, C++, XML, familiarity with linguistic issues, knowledge of FSTs preferable || Create an optional module to restore diacritics and accents on input text, and integrate it into the Apertium pipeline. || Many languages use diacritics and accents in normal writing, and Apertium is designed to use these, however in some places, especially for example. instant messaging, irc, searching in the web etc. these are often not used or untyped. This causes problems as for the engine, ''traduccion'' is not the same as ''traducción''. || [[User:Kevin Scannell|Kevin&nbsp;Scannell]], [[User:Trondtr|Trondtr]]<br />
|-<br />
!style="background-color: #cdcdef"| 4.&nbsp;Entry&nbsp;level ||colspan=2| || [[/Accent and diacritic restoration|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Geriaoueg vocabulary assistant'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| PHP, C++, XML || Extend [[Geriaoueg]] so that it works more reliably with broken HTML, with any given language pair (e.g. support for both [[lttoolbox]] and [[HFST]]. || [[Geriaoueg]] is a program that provides "popup" vocabulary assistance, something like BBC Vocab or Lingro. Currently it only works with Breton--French, Welsh--English and Spanish--Breton. This task would be to develop it to work with any language in our SVN and fix problems with processing and displaying non-standard HTML. || [[User:Francis Tyers|Francis&nbsp;Tyers]]<br />
|-<br />
!style="background-color: #cdcdef"| 4.&nbsp;Entry&nbsp;level ||colspan=2| || [[/Geriaoueg vocabulary assistant|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Apertium on your mobile'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Java, C++ || Port Apertium to iPhone and Android. || Apertium has a Java port, but it doesn't currently work on mobile telephones. Lots of people have mobile telephones, and some of them would like to have a translator there. || [[User:Jacob Nordfalk|Jacob&nbsp;Nordfalk]]<br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/Apertium on your mobile|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Closer integration with HFST'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C++, Autotools, XML || This is a set of subtasks to make it easier for Apertium developers to use the Helsinki Finite-State Toolkit (HFST). It will involve: Adjusting the HFST build process to allow for an Apertium-tailored install. Making an XML format for [[lexc]] designed with machine translation in mind. Adjusting the tokenisation code in <code>hfst-proc</code>. Making [[lttoolbox]] a possible backend for HFST. || HFST is a great toolkit for working with morphological transducers, but it is pretty difficult to install, and also not very well integrated with Apertium / doesn't really follow the Apertium way of doing things. We'd like to make it more closely integrated. || [[User:Francis Tyers|Francis&nbsp;Tyers]]<br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/Closer integration with HFST|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Corpus-based lexicalised feature transfer'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C++, NLP || Make a module that sits somewhere in the Apertium pipeline (somewhere after the lexical selection and before morphological generation) that sets features (eg. tags) based on a model generated from a corpus. || Let's get down to brass tacks, sometimes we get really inadequate translations even though you'd never hear stuff like that. One of those things is when we output something as definite when it is never used as definite. One way of dealing with this is a lot of rules and lists in transfer, but those are hard to do. So, how about looking at a corpus for information about some features like definiteness, aspect, evidentiality, impersonal/reflexive pronoun use in Romance languages etc. || [[User:Francis Tyers|Francis&nbsp;Tyers]], [[User:Jimregan|Jimregan]]<br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Corpus-based lexicalised feature transfer|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''''lint'' for Apertium'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Python, C++, XML, autotools || Make a program which tests Apertium data files for suspicious or unrecommended constructs (likely to be bugs). || || <br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/lint for Apertium|read&nbsp;more...]]<br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Corpus-based lexicalised feature transfer|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Apertium on Android with Necessitas QT'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C++, Android || Necessitas QT is a port of Qt on the Android Operating System and of the user-friendly Qt Creator Integration with Android. It allows programmers to compile C++ code and make it work on Android. Thus it hopefully can be used to build Apertium. || Apertium is efficient enough to work on a smartphone and would be the first translator to work without Internet connection (very useful when travelling abroad). A mechanism (i.e. temporary files) must be instrumented to overcome the unavailability of pipelines in Android.<br />
|| <br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/lint for Apertium|read&nbsp;more...]]<br />
|}<br />
<br />
;Notes<br />
<br />
* {{c14n}} stands for canonicalisation. These projects are intended to make it easier to develop new language pairs using Apertium without having to resort to non-Apertium modules.<br />
<br />
<br />
<br />
[[Category:Development]]<br />
[[Category:Google Summer of Code]]</div>Sortizhttps://wiki.apertium.org/w/index.php?title=Ideas_for_Google_Summer_of_Code&diff=32434Ideas for Google Summer of Code2012-02-28T14:41:48Z<p>Sortiz: /* List */</p>
<hr />
<div>{{TOCD}}<br />
This is the ideas page for [[Google Summer of Code]], here you can find ideas on interesting projects that would make Apertium more useful for people and improve or expand our functionality. If you have an idea please add it below, if you think you could mentor someone in a particular area, add your name to "Interested mentors" using <nowiki>~~~</nowiki> <br />
<br />
The page is intended as an overview of the kind of projects we have in mind. If one of them particularly piques your interest, please come and discuss with us on <code>#apertium</code> on <code>irc.freenode.net</code>, mail the [[Contact|mailing list]], or draw attention to yourself in some other way. <br />
<br />
Note that, if you have an idea that isn't mentioned here, we would be very interested to hear about it.<br />
<br />
Here are some more things you could look at:<br />
<br />
* [[Top tips for GSOC applications]] <br />
* Get in contact with one of our long-serving [[List of Apertium mentors|mentors]] &mdash; they are nice, honest!<br />
* Pages in the [[:Category:Development|development category]]<br />
* Resources that could be converted or expanded in the [[incubator]]. Consider doing or improving a language pair (see [[incubator]] and [[nursery]] for pairs that need work)<br />
* Unhammer's [[User:Unhammer/wishlist|wishlist]]<br />
* The [http://bugs.apertium.org/cgi-bin/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= open bugs] page on Bugzilla<br />
<br />
<!--<br />
See the list sorted by: {{comment|Do we need this? - [[User:Francis Tyers|Francis Tyers]]}}<br />
<br />
* [[/Difficulty|difficulty level]], <br />
* [[/Thematic|theme]]<br />
--><br />
==List==<br />
<br />
{|class="wikitable"<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Adopt a language pair'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
|XML, a scripting language (Python, Perl), good knowledge of the language pair adopted. || Take on an orphaned language pair, and bring it up to release quality results. What this quality will be will depend on the language pair adopted, and will need to be discussed with the prospective mentor. This will involve writing linguistic data (including morphological rules and transfer rules &mdash; which are specified in a declarative language &mdash; and possibly [[Constraint Grammar]] rules if that is relevant) || Apertium has a few pairs of languages (e.g. mt-he, ga-gd, ur-hi, id-ms, pl-cs, etc...) that are orphaned, they don't have active maintainers. A lot of these pairs have a lot of work already put in, just need another few months to get them to release quality. See also [[Incubator]] || [[User:Francis Tyers|Francis Tyers]], [[User:Jimregan|Jimregan]], [[User:Kevin Scannell|Kevin&nbsp;Scannell]], [[User:Trondtr|Trondtr]], [[User:Unhammer|Unhammer]], [[User:Darthxaher|Darthxaher]], [[User:Firespeaker|Firespeaker]], [[User:Hectoralos|Hectoralos]]<br />
|-<br />
!style="background-color: #cdcdef"| 4.&nbsp;Entry&nbsp;level ||colspan=2| || [[/Adopt a language pair|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Discontiguous multiwords'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
|C++, Knowledge of FSTs || The task will be to develop, or adapt a module to deal with these kind of contiguous multiword expressions, for example, taking 'liggja ekki fyrir' and reordering it as 'liggja# fyrir ekki'. || In many languages, such as English, Norwegian and Icelandic, there are discontiguous multiwords, e.g. phrasal verbs, that we cannot easily support. For example 'liggja ekki fyrir' in Icelandic should be translated in English as 'to be not clear', but we cannot have 'liggja fyrir' as a traditional multiword because of the extra 'adverb', or it could even be a whole NP. || [[User:Francis Tyers|Francis Tyers]], [[User:Jimregan|Jimregan]]<br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/Discontiguous multiwords|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Flag diacritics in lttoolbox'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C++ or Java, XML, Knowledge of FSTs || Adapt [[lttoolbox]] to elegantly use flag diacritics. Flag diacritics are a way of avoiding transducer size blow-up by discarding impossible paths at runtime as opposed to compile time. || This will involve designing some changes to our XML dictionary format (see [[lttoolbox]], and implementing the associated changes in the FST compiling processing code. The reason behind this is that many languages have prefix inflection, and we cannot currently deal with this without either making paradigms useless, or overanalysing (e.g. returning analyses where none exist). Flag diacritics (or constraints) would allow us to restrict overanalysis without blowing up the size of our dictionaries. || [[User:Francis Tyers|Francis Tyers]]&nbsp;(C++), [[User:Jacob Nordfalk|Jacob Nordfalk]] (Java)<br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Flag diacritics in lttoolbox|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Rule-based finite-state disambiguation'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| XML, C++ || Currently Apertium only has a bigram/trigram part-of-speech tagger. The objective of this task would be to implement a disambiguation framework for Apertium that can be expressed as a finite-state transducer. It might be a good idea to express this as constraint rules, in a novel XML-based file format. || For some languages, bigram/trigram POS disambiguation really doesn't work, especially when you want to disambiguate morphology (e.g. number, case) along with part-of-speech. So far we've been using [[constraint grammar]] for some of these languages. But although Constraint Grammar is great and powerful, it is also pretty slow. It would be a good idea to look at LanguageTool, and IceParser and Apertium's own [[apertium-lex-tools]] to get ideas on how this might be accomplished. || [[User:Francis Tyers|Francis Tyers]] <br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Rule-based finite-state disambiguation|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Complex multiwords'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Java or C++, XML, Knowledge of FSTs || Write a bidirectional module for specifying complex multiword units, for example ''dirección general'' and ''zračna luka''. See ''[[Multiwords]]'' for more information. || Although in the Romance languages it is not a big problem, as soon as you start to get to languages with cases (e.g. Serbo-Croatian, Slovenian, German, etc.) the problem comes that you can't define a multiword of <code>adj nom</code> because the adjective has a lot of inflection. || [[User:Jimregan|Jimregan]]<br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Complex multiwords|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Optimise the VM for transfer'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Python, C++, XML, code optimisation, JIT techniques, etc. || The current VM for the transfer architecture of Apertium is up to five times slower than the XML tree-walking implementation. The job of this task is to optimise the C++ code to make it faster than XML tree-walking. || The rationale behind this is that XML tree-walking is quite slow and CPU intensive. In modern (3 or more stage) pairs, transfer takes up most of the CPU. There are other options, like [[Bytecode for transfer]], but we would like something that does not require external libraries and is adapted specifically for Apertium. || [[User:Sortiz|Sortiz]]<br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/Optimise the VM for transfer|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Accent and diacritic restoration'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C, C++, XML, familiarity with linguistic issues, knowledge of FSTs preferable || Create an optional module to restore diacritics and accents on input text, and integrate it into the Apertium pipeline. || Many languages use diacritics and accents in normal writing, and Apertium is designed to use these, however in some places, especially for example. instant messaging, irc, searching in the web etc. these are often not used or untyped. This causes problems as for the engine, ''traduccion'' is not the same as ''traducción''. || [[User:Kevin Scannell|Kevin&nbsp;Scannell]], [[User:Trondtr|Trondtr]]<br />
|-<br />
!style="background-color: #cdcdef"| 4.&nbsp;Entry&nbsp;level ||colspan=2| || [[/Accent and diacritic restoration|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Geriaoueg vocabulary assistant'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| PHP, C++, XML || Extend [[Geriaoueg]] so that it works more reliably with broken HTML, with any given language pair (e.g. support for both [[lttoolbox]] and [[HFST]]. || [[Geriaoueg]] is a program that provides "popup" vocabulary assistance, something like BBC Vocab or Lingro. Currently it only works with Breton--French, Welsh--English and Spanish--Breton. This task would be to develop it to work with any language in our SVN and fix problems with processing and displaying non-standard HTML. || [[User:Francis Tyers|Francis&nbsp;Tyers]]<br />
|-<br />
!style="background-color: #cdcdef"| 4.&nbsp;Entry&nbsp;level ||colspan=2| || [[/Geriaoueg vocabulary assistant|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Apertium on your mobile'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Java, C++ || Port Apertium to iPhone and Android. || Apertium has a Java port, but it doesn't currently work on mobile telephones. Lots of people have mobile telephones, and some of them would like to have a translator there. || [[User:Jacob Nordfalk|Jacob&nbsp;Nordfalk]]<br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/Apertium on your mobile|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Closer integration with HFST'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C++, Autotools, XML || This is a set of subtasks to make it easier for Apertium developers to use the Helsinki Finite-State Toolkit (HFST). It will involve: Adjusting the HFST build process to allow for an Apertium-tailored install. Making an XML format for [[lexc]] designed with machine translation in mind. Adjusting the tokenisation code in <code>hfst-proc</code>. Making [[lttoolbox]] a possible backend for HFST. || HFST is a great toolkit for working with morphological transducers, but it is pretty difficult to install, and also not very well integrated with Apertium / doesn't really follow the Apertium way of doing things. We'd like to make it more closely integrated. || [[User:Francis Tyers|Francis&nbsp;Tyers]]<br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/Closer integration with HFST|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Corpus-based lexicalised feature transfer'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C++, NLP || Make a module that sits somewhere in the Apertium pipeline (somewhere after the lexical selection and before morphological generation) that sets features (eg. tags) based on a model generated from a corpus. || Let's get down to brass tacks, sometimes we get really inadequate translations even though you'd never hear stuff like that. One of those things is when we output something as definite when it is never used as definite. One way of dealing with this is a lot of rules and lists in transfer, but those are hard to do. So, how about looking at a corpus for information about some features like definiteness, aspect, evidentiality, impersonal/reflexive pronoun use in Romance languages etc. || [[User:Francis Tyers|Francis&nbsp;Tyers]], [[User:Jimregan|Jimregan]]<br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Corpus-based lexicalised feature transfer|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''''lint'' for Apertium'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Python, C++, XML, autotools || Make a program which tests Apertium data files for suspicious or unrecommended constructs (likely to be bugs). || || <br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/lint for Apertium|read&nbsp;more...]]<br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Corpus-based lexicalised feature transfer|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Apertium on Android with Necessitas QT'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C++, Android || Necessitas QT is a port of Qt on the Android Operating System and of the user-friendly Qt Creator Integration with Android. It allows programmers to compile C++ code and make it work on Android. || Apertium is efficient enough to work on a smartphone and would be the first translator to work without Internet connection (very useful when travelling abroad). <br />
<br />
|| <br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/lint for Apertium|read&nbsp;more...]]<br />
|}<br />
<br />
;Notes<br />
<br />
* {{c14n}} stands for canonicalisation. These projects are intended to make it easier to develop new language pairs using Apertium without having to resort to non-Apertium modules.<br />
<br />
<br />
<br />
[[Category:Development]]<br />
[[Category:Google Summer of Code]]</div>Sortizhttps://wiki.apertium.org/w/index.php?title=Ideas_for_Google_Summer_of_Code&diff=32433Ideas for Google Summer of Code2012-02-28T14:39:57Z<p>Sortiz: /* List */</p>
<hr />
<div>{{TOCD}}<br />
This is the ideas page for [[Google Summer of Code]], here you can find ideas on interesting projects that would make Apertium more useful for people and improve or expand our functionality. If you have an idea please add it below, if you think you could mentor someone in a particular area, add your name to "Interested mentors" using <nowiki>~~~</nowiki> <br />
<br />
The page is intended as an overview of the kind of projects we have in mind. If one of them particularly piques your interest, please come and discuss with us on <code>#apertium</code> on <code>irc.freenode.net</code>, mail the [[Contact|mailing list]], or draw attention to yourself in some other way. <br />
<br />
Note that, if you have an idea that isn't mentioned here, we would be very interested to hear about it.<br />
<br />
Here are some more things you could look at:<br />
<br />
* [[Top tips for GSOC applications]] <br />
* Get in contact with one of our long-serving [[List of Apertium mentors|mentors]] &mdash; they are nice, honest!<br />
* Pages in the [[:Category:Development|development category]]<br />
* Resources that could be converted or expanded in the [[incubator]]. Consider doing or improving a language pair (see [[incubator]] and [[nursery]] for pairs that need work)<br />
* Unhammer's [[User:Unhammer/wishlist|wishlist]]<br />
* The [http://bugs.apertium.org/cgi-bin/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= open bugs] page on Bugzilla<br />
<br />
<!--<br />
See the list sorted by: {{comment|Do we need this? - [[User:Francis Tyers|Francis Tyers]]}}<br />
<br />
* [[/Difficulty|difficulty level]], <br />
* [[/Thematic|theme]]<br />
--><br />
==List==<br />
<br />
{|class="wikitable"<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Adopt a language pair'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
|XML, a scripting language (Python, Perl), good knowledge of the language pair adopted. || Take on an orphaned language pair, and bring it up to release quality results. What this quality will be will depend on the language pair adopted, and will need to be discussed with the prospective mentor. This will involve writing linguistic data (including morphological rules and transfer rules &mdash; which are specified in a declarative language &mdash; and possibly [[Constraint Grammar]] rules if that is relevant) || Apertium has a few pairs of languages (e.g. mt-he, ga-gd, ur-hi, id-ms, pl-cs, etc...) that are orphaned, they don't have active maintainers. A lot of these pairs have a lot of work already put in, just need another few months to get them to release quality. See also [[Incubator]] || [[User:Francis Tyers|Francis Tyers]], [[User:Jimregan|Jimregan]], [[User:Kevin Scannell|Kevin&nbsp;Scannell]], [[User:Trondtr|Trondtr]], [[User:Unhammer|Unhammer]], [[User:Darthxaher|Darthxaher]], [[User:Firespeaker|Firespeaker]], [[User:Hectoralos|Hectoralos]]<br />
|-<br />
!style="background-color: #cdcdef"| 4.&nbsp;Entry&nbsp;level ||colspan=2| || [[/Adopt a language pair|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Discontiguous multiwords'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
|C++, Knowledge of FSTs || The task will be to develop, or adapt a module to deal with these kind of contiguous multiword expressions, for example, taking 'liggja ekki fyrir' and reordering it as 'liggja# fyrir ekki'. || In many languages, such as English, Norwegian and Icelandic, there are discontiguous multiwords, e.g. phrasal verbs, that we cannot easily support. For example 'liggja ekki fyrir' in Icelandic should be translated in English as 'to be not clear', but we cannot have 'liggja fyrir' as a traditional multiword because of the extra 'adverb', or it could even be a whole NP. || [[User:Francis Tyers|Francis Tyers]], [[User:Jimregan|Jimregan]]<br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/Discontiguous multiwords|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Flag diacritics in lttoolbox'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C++ or Java, XML, Knowledge of FSTs || Adapt [[lttoolbox]] to elegantly use flag diacritics. Flag diacritics are a way of avoiding transducer size blow-up by discarding impossible paths at runtime as opposed to compile time. || This will involve designing some changes to our XML dictionary format (see [[lttoolbox]], and implementing the associated changes in the FST compiling processing code. The reason behind this is that many languages have prefix inflection, and we cannot currently deal with this without either making paradigms useless, or overanalysing (e.g. returning analyses where none exist). Flag diacritics (or constraints) would allow us to restrict overanalysis without blowing up the size of our dictionaries. || [[User:Francis Tyers|Francis Tyers]]&nbsp;(C++), [[User:Jacob Nordfalk|Jacob Nordfalk]] (Java)<br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Flag diacritics in lttoolbox|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Rule-based finite-state disambiguation'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| XML, C++ || Currently Apertium only has a bigram/trigram part-of-speech tagger. The objective of this task would be to implement a disambiguation framework for Apertium that can be expressed as a finite-state transducer. It might be a good idea to express this as constraint rules, in a novel XML-based file format. || For some languages, bigram/trigram POS disambiguation really doesn't work, especially when you want to disambiguate morphology (e.g. number, case) along with part-of-speech. So far we've been using [[constraint grammar]] for some of these languages. But although Constraint Grammar is great and powerful, it is also pretty slow. It would be a good idea to look at LanguageTool, and IceParser and Apertium's own [[apertium-lex-tools]] to get ideas on how this might be accomplished. || [[User:Francis Tyers|Francis Tyers]] <br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Rule-based finite-state disambiguation|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Complex multiwords'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Java or C++, XML, Knowledge of FSTs || Write a bidirectional module for specifying complex multiword units, for example ''dirección general'' and ''zračna luka''. See ''[[Multiwords]]'' for more information. || Although in the Romance languages it is not a big problem, as soon as you start to get to languages with cases (e.g. Serbo-Croatian, Slovenian, German, etc.) the problem comes that you can't define a multiword of <code>adj nom</code> because the adjective has a lot of inflection. || [[User:Jimregan|Jimregan]]<br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Complex multiwords|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Optimise the VM for transfer'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Python, C++, XML, code optimisation, JIT techniques, etc. || The current VM for the transfer architecture of Apertium is up to five times slower than the XML tree-walking implementation. The job of this task is to optimise the C++ code to make it faster than XML tree-walking. || The rationale behind this is that XML tree-walking is quite slow and CPU intensive. In modern (3 or more stage) pairs, transfer takes up most of the CPU. There are other options, like [[Bytecode for transfer]], but we would like something that does not require external libraries and is adapted specifically for Apertium. || [[User:Sortiz|Sortiz]]<br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/Optimise the VM for transfer|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Accent and diacritic restoration'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C, C++, XML, familiarity with linguistic issues, knowledge of FSTs preferable || Create an optional module to restore diacritics and accents on input text, and integrate it into the Apertium pipeline. || Many languages use diacritics and accents in normal writing, and Apertium is designed to use these, however in some places, especially for example. instant messaging, irc, searching in the web etc. these are often not used or untyped. This causes problems as for the engine, ''traduccion'' is not the same as ''traducción''. || [[User:Kevin Scannell|Kevin&nbsp;Scannell]], [[User:Trondtr|Trondtr]]<br />
|-<br />
!style="background-color: #cdcdef"| 4.&nbsp;Entry&nbsp;level ||colspan=2| || [[/Accent and diacritic restoration|read&nbsp;more...]]<br />
|-<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Geriaoueg vocabulary assistant'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| PHP, C++, XML || Extend [[Geriaoueg]] so that it works more reliably with broken HTML, with any given language pair (e.g. support for both [[lttoolbox]] and [[HFST]]. || [[Geriaoueg]] is a program that provides "popup" vocabulary assistance, something like BBC Vocab or Lingro. Currently it only works with Breton--French, Welsh--English and Spanish--Breton. This task would be to develop it to work with any language in our SVN and fix problems with processing and displaying non-standard HTML. || [[User:Francis Tyers|Francis&nbsp;Tyers]]<br />
|-<br />
!style="background-color: #cdcdef"| 4.&nbsp;Entry&nbsp;level ||colspan=2| || [[/Geriaoueg vocabulary assistant|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Apertium on your mobile'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Java, C++ || Port Apertium to iPhone and Android. || Apertium has a Java port, but it doesn't currently work on mobile telephones. Lots of people have mobile telephones, and some of them would like to have a translator there. || [[User:Jacob Nordfalk|Jacob&nbsp;Nordfalk]]<br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/Apertium on your mobile|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Closer integration with HFST'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C++, Autotools, XML || This is a set of subtasks to make it easier for Apertium developers to use the Helsinki Finite-State Toolkit (HFST). It will involve: Adjusting the HFST build process to allow for an Apertium-tailored install. Making an XML format for [[lexc]] designed with machine translation in mind. Adjusting the tokenisation code in <code>hfst-proc</code>. Making [[lttoolbox]] a possible backend for HFST. || HFST is a great toolkit for working with morphological transducers, but it is pretty difficult to install, and also not very well integrated with Apertium / doesn't really follow the Apertium way of doing things. We'd like to make it more closely integrated. || [[User:Francis Tyers|Francis&nbsp;Tyers]]<br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/Closer integration with HFST|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Corpus-based lexicalised feature transfer'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| C++, NLP || Make a module that sits somewhere in the Apertium pipeline (somewhere after the lexical selection and before morphological generation) that sets features (eg. tags) based on a model generated from a corpus. || Let's get down to brass tacks, sometimes we get really inadequate translations even though you'd never hear stuff like that. One of those things is when we output something as definite when it is never used as definite. One way of dealing with this is a lot of rules and lists in transfer, but those are hard to do. So, how about looking at a corpus for information about some features like definiteness, aspect, evidentiality, impersonal/reflexive pronoun use in Romance languages etc. || [[User:Francis Tyers|Francis&nbsp;Tyers]], [[User:Jimregan|Jimregan]]<br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Corpus-based lexicalised feature transfer|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''''lint'' for Apertium'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Python, C++, XML, autotools || Make a program which tests Apertium data files for suspicious or unrecommended constructs (likely to be bugs). || || <br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/lint for Apertium|read&nbsp;more...]]<br />
|-<br />
!style="background-color: #efcdcd"|2.&nbsp;Hard ||colspan=2| || [[/Corpus-based lexicalised feature transfer|read&nbsp;more...]]<br />
|-<br />
!colspan=4 style="background-color: #cdcdcd"|'''Apertium on Android with Necessitas QT'''<br />
|-<br />
|align=center| '''How ?'''<br/><small>(required skills)</small> ||align=center| '''What ?'''<br/><small>(description)</small> ||align=center| '''Why ?'''<br/><small>(rationale)</small> ||align=center| '''Who ?'''<br/><small>(mentors)</small><br />
|-<br />
| Python, C++, XML, autotools || Make a program which tests Apertium data files for suspicious or unrecommended constructs (likely to be bugs). || || <br />
|-<br />
!style="background-color: #cdefcd"|3.&nbsp;Medium ||colspan=2| || [[/lint for Apertium|read&nbsp;more...]]<br />
|}<br />
<br />
;Notes<br />
<br />
* {{c14n}} stands for canonicalisation. These projects are intended to make it easier to develop new language pairs using Apertium without having to resort to non-Apertium modules.<br />
<br />
<br />
<br />
[[Category:Development]]<br />
[[Category:Google Summer of Code]]</div>Sortiz