Difference between revisions of "Google Summer of Code"

From Proxecto Trasno
(normas)
(About this webpage)
Line 4: Line 4:
 
This webpage will contain all information related to trasno at GSoC 2011.  
 
This webpage will contain all information related to trasno at GSoC 2011.  
 
* You can add new ideas using as a template other ideas.  
 
* You can add new ideas using as a template other ideas.  
* You shall not edit other content of this webpage. Any objection shall be addressed at info at trasno.net.  
+
* You shall not edit any other content of this webpage but "ideas". Do not edit or assign mentors or consultants. Any objection shall be addressed at info at trasno.net.  
* All content shall be in English. If your writing skills are not good enough write in Galician and immediately as other to translate.  
+
* All content shall be in English. If your writing skills are not good enough write in Galician and immediately as other to translate.
  
 
== Ideas ==
 
== Ideas ==

Revision as of 18:15, 12 March 2011

This is the webpage for Proxecto Trasno GSoC 2011 application. Hope we are in as a mentor organisation. We'll know very soon :)

About this webpage

This webpage will contain all information related to trasno at GSoC 2011.

  • You can add new ideas using as a template other ideas.
  • You shall not edit any other content of this webpage but "ideas". Do not edit or assign mentors or consultants. Any objection shall be addressed at info at trasno.net.
  • All content shall be in English. If your writing skills are not good enough write in Galician and immediately as other to translate.

Ideas

Ideas should relate to l10n or i18n. Areas considered are:

  • CAT tool improvements
  • work on dictionaries or thesaurus

More detailed ideas, of which partial implementations could be chosen as GSoC, follow.

Pology integration into Lokalize

Brief explanation: Pology integration into Lokalize so QA tools are directly available from within the UI.

Expected results:

  • Lokalize is expected to act as a pology client
  • QA analysis should be accesible from within the project tab and when switching between translation units
  • Any file accessed by pology's scripts or hooks should be modifiable by the user at any time.
  • Specialised dictionary management through a built in Lokalize menu
  • Spell check-in uses specialised dictionaries on the fly
  • Translator tips on hook behaviour(#|, no-check-spell e # well-spelled:) edition from within file edition window
  • check-rules hook can be configured and called from either the project tab or from the unit translation panel, by request or on the fly. Show "# skip-rule:" option when running live.
  • Grammar check-in through check-grammar hook.
  • Agárdase que o usuario poida aplicar a comprobación de validez segundo os criterios do proxecto (vale, na actualidade só hai para kde e para o wesnoth).

Knowledge prerequisites:

  • KDE development stack (Qt/C++ and git)

Mentor: Marce Villarino Consultant: Miguel Branco


Pology enhacement: add check-spell-hunspell hook

Brief explanation: hunspell's based grammar checker.

Expected results:

  • Pology's tool development that makes use of hunspell to ckeck grammar
  • Use of specialised dictionaries so new affixes info can be added

Knowledge prerequisites:

Mentor: TBD Consultant: TBD

LanguageTool rules enhacement for galician language

Brief explanation: LanguageTool stemming and segmentation improvements for galician language. New rules definition.

Mellora da segmentación e engadido de máis regras.

Expected results:

  • Galician languaguage grammar tool development based upon LanguageTool, similar in number of grammar rules to Golfiño.
  • Phrase segmentation improvement.

Knowledge prerequisites:

Mentor: TBD Consultant: TBD

Web based terminology discussion tool

Brief explanation:

Expected results:

  • Should be able to handle several multilingual glossaries
  • Should be able to handle terminologial entries information like definitions, concept relationships, part of speech...
  • Should be able to provide a discussion thread for language in each terminological entry
  • Should provide search capabilities
  • Should be able to export the glossaries to TBX (TermBase eXchange ISO 30042) format
  • Should provide a way to integrate with other already existing localization tools

Knowledge prerequisites: no requirements. But the knowledge of what terminology is, TBX format understanding, programming language knowledge (preferrably Python) or even knowledge of web development frameworks (preferrably Django) will be appreciated.

Mentor: Consultant:

Submitting ideas

Address your ideas at info at trasno.net .

Mentors

Mentors should apply at info at trasno.net

Students

How to apply

If you're willing to implement any of the ideas detailed here or some of yours, apply for the job!. Write to info at trasno.net with an answer to this questions:

  • Who are you?
  • Where do you live?
  • What's your academic background?
  • Do you have experience on localization or internationalization?
  • Are you joining an idea? Which one?
  • Are you proposing a new idea?. Tell us about it.
  • Why are you the right person for this task?
  • To what extent are you familiar with the software you're proposing to work with? Have you used it? Have you read the source? Have you modified the source?
  • How many hours are you going to work on this a week? 10? 20? 30? 40?
  • Do you have other commitments that we should know about?
  • Are you comfortable working independently under a supervisor or mentor who is several miles away?

You can address us in Galician, Portuguese or English. If you application is accepted you will be assigned a mentor and a consultant. If your not selected we could reach to you in case other student leaves his/her position.

Please, go to GSoC 2011 web page for more details or ask us.