Difference between revisions of "Google Summer of Code"

From Proxecto Trasno
(Pology enhacement: add check-spell-hunspell hook)
(LanguageTool rules enhacement for galician language)
Line 43: Line 43:
  
 
=== LanguageTool rules enhacement for galician language ===
 
=== LanguageTool rules enhacement for galician language ===
'''Brief explanation:''' Mellora da segmentación e engadido de máis regras.
+
'''Brief explanation:''' [http://www.languagetool.org/ LanguageTool] stemming and segmentation improvements for galician language. New rules definition.
 +
 
 +
Mellora da segmentación e engadido de máis regras.
  
 
'''Expected results:'''
 
'''Expected results:'''
* Agárdase obter un sistema de corrección gramatical baseado no LanguageTool cunha cantidade e amplitude de regras semellante ao Golfiño e mellorar a segmentación en oracións que se fai na actualidade para o idioma galeno no LT (fai falla para mellorar a calidade dos resultados)
+
* Galician languaguage grammar tool development based upon LanguageTool, similar in number of grammar rules to [http://wiki.mancomun.org/index.php/Golfi%C3%B1o._Corrector_gramatical_para_OpenOffice.org Golfiño].
 +
* Phrase segmentation improvement.
  
 
'''Knowledge prerequisites:'''
 
'''Knowledge prerequisites:'''
  
'''Mentor:'''  
+
'''Mentor:'''
 
+
TBD
 
+
'''Consultant:'''
 +
TBD
  
 
=== Web based terminology discussion tool ===
 
=== Web based terminology discussion tool ===

Revision as of 17:58, 12 March 2011

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:

Submitting ideas

Mentors

Students

How to apply