Editing Google Summer of Code

From Proxecto Trasno

Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.

The system administrator who locked it offered this explanation: Esta wiki está temporalmente en modo de só lectura

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
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:
+
to be filled
* 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).
 
 
 
'''Knowledge prerequisites:'''
 
* KDE development stack (Qt/C++ and git)
 
 
 
'''Mentor:''' Marce Villarino
 
'''Consultant:''' Miguel Branco
 
 
 
 
 
=== Pology enhacement: add check-spell-hunspell hook ===
 
'''Brief explanation:''' [http://en.wikipedia.org/wiki/Hunspell 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:''' [http://www.languagetool.org/ 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 [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.
 

Please note that all contributions to Proxecto Trasno are considered to be released under the Attribution-Share Alike 3.0 Unported (see Proxecto Trasno:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)