Intellego/GSoC/2014: Difference between revisions

(Clean up formatting and wikimarkup.)
 
(5 intermediate revisions by 3 users not shown)
Line 20: Line 20:


==== Week 1 ====
==== Week 1 ====
* Create a bilingual termbase of terminology consisting of Mozilla-specific terminology from Mozilla l10n resources.
* Create a bilingual termbase of terminology consisting of Mozilla-specific terminology from Mozilla l10n resources. ({{bug|983140}})


==== Week 2 ====
==== Week 2 ====
* Create a front-end web portal UI in which the user will simply enter a URL and click a button to execute the MT results.
* Create a front-end web portal UI in which the user will simply enter a URL and click a button to execute the MT results. ({{bug|983142}})
* Create a back-end, Python-based program that will, given a URL, extract the DOM text nodes from the associated webpage.
* Create a back-end, Python-based program that will, given a URL, extract the DOM text nodes from the associated webpage. ({{bug|983143}})


==== Week 3 ====
==== Week 3 ====
* Filter out DOM text nodes with untranslatable (or non-translatable) text.
* Filter out DOM text nodes with untranslatable (or non-translatable) text. ({{bug|983257}})


==== Week 4 ====
==== Week 4 ====
* Search the translatable DOM text nodes (the source) for source terminology matches in the bilingual termbase.
* Search the translatable DOM text nodes (the source) for source terminology matches in the bilingual termbase. ({{bug|983266}})


==== Week 5 ====
==== Week 5 ====
* Map the source terminology to the matching target terminology from the termbase.
* Map the source terminology to the matching target terminology from the termbase. ({{bug|983144}})


==== Week 6 ====
==== Week 6 ====
* All-At-Once Replacement Method: Regenerate the DOM with the replaced terminology, output to a new webpage, and render it.
* All-At-Once Replacement Method: Regenerate the DOM with the replaced terminology, output to a new webpage, and render it. ({{bug|983146}})


==== Week 7 ====
==== Week 7 ====
* On-the-Fly Replacement Method: Perform the terminology replacement operation on the DOM segment by segment, instead of extracting all text nodes from the DOM at once.
* On-the-Fly Replacement Method: Perform the terminology replacement operation on the DOM segment by segment, instead of extracting all text nodes from the DOM at once. ({{bug|983148}})


==== Week 8 ====
==== Week 8 ====
* Evaluate each method (all-at-once or on-the-fly) for efficiency and analyze whether it would be beneficial to use one method over the other, or whether it would be better to offer a choice of either.
* Evaluate each method (all-at-once or on-the-fly) for efficiency and analyze whether it would be beneficial to use one method over the other, or whether it would be better to offer a choice of either. ({{bug|983250}})


=== Final deliverable ===
=== Final deliverable ===
* Automatic terminology translation tool consisting of a web interface and a server-side tool. A user will insert the URL of a source language web site and the tool will return the rendered target language website containing partially translated content.
* Automatic terminology translation tool consisting of a web interface and a server-side tool. A user will insert the URL of a source language web site and the tool will return the rendered target language website containing partially translated content. ({{bug|983138}})


== Interested students ==
== Interested students ==
Line 73: Line 73:
| [http://github.com/viperfx Github]
| [http://github.com/viperfx Github]
|  
|  
|}
|-
| Sudheesh Singanamalla
| sudheesh1994[at]yahoo.com
| [http://www.sudheesh.info Website]
| [http://github.com/sudheesh001 Github]
|-
| Rishabh Roy
| rishabhsixfeet[at]gmail.com
|
| [http://github.com/rishabhsixfeet Github]
| python developer making tools to be used by mass
|-
}


== Team liaisons ==
== Team liaisons ==
3

edits