Difference between revisions of "Google Summer of Code"

From Proxecto Trasno
(→‎About this webpage)
 
(20 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
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 others to provide translation.
 +
 
== Ideas ==
 
== 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:'''
 +
[http://techbase.kde.org/Localization/Tools/Pology Pology] integration into [http://userbase.kde.org/Lokalize Lokalize] so [http://en.wikipedia.org/wiki/Quality_assessment 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).
  
−
* desenvolvemento de engadidos para ferramenta CAT [any]
+
'''Knowledge prerequisites:'''
−
* mellora no motor de diccionario [hunspell]
+
* KDE development stack (Qt/C++ and git)
−
* software de xestión de thesaurus
 
−
* desenvolvemento de enchant
 
  
−
=== Integrate Pology in Lokalize for providing Quality Assesment capabilities ===
+
'''Mentor:''' Marce Villarino
 +
'''Consultant:''' Miguel Branco
  
−
'''Project:''' Integracion de pology con Lokalize para incorporar a esta
 
−
ferramenta de TAO capacidades de QA
 
  
−
'''Brief explanation:''' Integrar dentro de Lokalize determinadas utilidades
+
=== Pology enhacement: add check-spell-hunspell hook ===
−
do pology (verificación da ortografía, gramatica, regras e outras) de
+
'''Brief explanation:''' [http://en.wikipedia.org/wiki/Hunspell hunspell]'s based grammar checker.
−
xeito que se poidan utilizar sen ir á liña de ordes.
 
  
 
'''Expected results:'''
 
'''Expected results:'''
−
* Agárdase que o lokalize se comporte como cliente do pology.
+
* Pology's tool development that makes use of hunspell to ckeck grammar
−
* Agárdase que o usuario poida executar e obter resultados da comprobación de regras tanto a xeito de resumo desde a lapela do proxecto como no momento de cambiar o estado da unidade de tradución.
+
* Use of specialised dictionaries so new affixes info can be added
−
* Agárdase que o usuario poida modificar calquera ficheiro de datos utilizado directamente polo script ou hook do pology que estexa a utilizar.
 
−
* Agárdase que o usuario poida crear e editar os ficheiros de dicionario especializado que considere oportuno mediante unha gui que ofreza o lokalize. * A comprobación ortográfica utilizará estes dicionarios tanto se é executada desde un menú como se a executa ao vivo.
 
−
* As indicacións do tradutor que afectan o comportamente destes hooks (#|, no-check-spell e # well-spelled:) deben poder inserirse desde a xanela de edición do ficheiro.
 
−
* gárdase que o usuario poida aplicar a comprobación de regras mediante o hook check-rules, configurando calquera parámetro deste hook. Esta comprobación poderá executarse de dous xeitos:
 
−
a) Mediante a lapela do proxecto, onde se aplicará a un só ficheiro
 
−
ou cartafol, abríndose no segundo plano os ficheiros
 
−
b) Ao vivo, durante a edición da UT, neste caso, no caso de saltar
 
−
regras, antes de pasar a outra UT deberá notificar o usuario indicando
 
−
que regras non se satisfan, e ofrecendo a opción de engadir o
 
−
indicador de omisión de regras (# skip-rule: regra1, regra2) ou de
 
−
editar a regra.
 
−
Agárdase que o usuario poida aplicar a comprobación gramatical
 
−
mediante o hook check-grammar.
 
−
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:'''
  
−
Project: Mellora no pology engadíndolle un hook check-spell-hunspell
+
'''Mentor:'''
−
Brief explanation: Creación dun hook que empregue hunspell para a
+
TBD
−
corrección ortográfica
+
'''Consultant:'''
−
Expected results
+
TBD
−
Agárdase que se cree un hook para o pology que empregue o hunspell
 
−
como motor de corrección ortográfica permitindo empregar dicionarios
 
−
especializados no formato do hunspell, co que se pode incluir
 
−
información de afixos nel (aforrando moita extensión e facendo máis
 
−
completos os dicionarios)
 
  
−
Project: Mellora das regras para a lingua galega do LanguageTool
+
=== 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.
−
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)
 
  
 +
'''Expected results:'''
 +
* 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:'''
  
 +
'''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 ([http://www.lisa.org/Term-Base-eXchange-TBX.32.0.html 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 ==
 
== Submitting ideas ==
 +
Address your ideas at info at trasno.net .
 +
 
= Mentors =
 
= Mentors =
 +
Mentors should apply at info at trasno.net
 +
 
= Students =
 
= Students =
 
== How to apply ==
 
== 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.

Latest revision as of 15:32, 14 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[edit]

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 others to provide translation.

Ideas[edit]

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[edit]

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[edit]

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[edit]

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

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[edit]

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[edit]

Address your ideas at info at trasno.net .

Mentors[edit]

Mentors should apply at info at trasno.net

Students[edit]

How to apply[edit]

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.

Retrieved from "http://wiki.trasno.gal/index.php?title=Google_Summer_of_Code&oldid=1873"