Search results
Jump to navigation
Jump to search
- ...d, and write 5 lexical selection rules that select the correct translation in the relevant context. [[Category:Tasks for Google Code-in|Setup and add lexical selection]]1 KB (165 words) - 14:19, 29 October 2013
- ...requency. The lemma of a word is it's "base form" (the form you might find in a dictionary) ...t. Work from top to bottom. After each asterisk '<code><nowiki>*</nowiki></code>' you should replace the surface form with the lemma.2 KB (207 words) - 16:21, 14 November 2013
- * Xchat: write a plugin reads in text from the highlighted channel and, if it contains three asterisks (***) [[Category:Ideas for Google Summer of Code|Apertium in chat clients]]457 bytes (65 words) - 21:45, 10 March 2014
- ...://summerofcode.withgoogle.com/projects/#5878649350258688 Google Summer of Code 2018 project] — Tatar-Bashkir machine translation. Lexicons in bak.lexc were changed to correspond to the ones in tat.lexc, missing lexicons and tags were added to bak.lexc and new rules we2 KB (262 words) - 13:17, 14 August 2018
- ...m-html-tools]] has seen some prototypes for spell-checking interfaces (all in stale PRs and branches on GitHub), but none have ended up being quite ready ** Should automatically detect available voikko modes in language modules (might need to standardise how these are done, but check [1 KB (166 words) - 22:19, 18 January 2021
- * Find a language pair of your choice in Apertium and install it. (see [[Minimal installation from SVN]]) ...stipend installment(s)]. At least you tried! And, hopefully, learnt a lot in the process.2 KB (377 words) - 19:18, 25 January 2023
- This page gives a roadmap of features which we hope will be available in future Apertium releases. ** Parser (e.g. [[Ideas for Google Summer of Code/Robust recursive transfer]])1 KB (160 words) - 10:44, 23 September 2016
- Apertium structural transfer rules are currently encoded in XML-based formats. These are very overt and clear, but clumsy and may be ha ...raphical user interface to write structural transfer rules (one that reads in (a subset of) the current XML-based language, allows for a graphical, intui1 KB (162 words) - 01:11, 18 August 2015
- * [[Plugins#In progress]] [[Category:Google Summer of Code|Report 2014]]3 KB (305 words) - 08:31, 13 January 2015
- Daniel Huang, Google Code In 2012 ...archive.org/web/20071101095455/http://www.ethnologue.com/show_language.asp?code=uzn Northern dialect]5 KB (578 words) - 22:55, 27 November 2012
- This page was written by Jatin Luthra, a 2016 Google Code-in student, which explains how to install Apertium on Alpine Linux706 bytes (102 words) - 19:50, 15 December 2016
- Daniel Huang, Google Code In 2012889 bytes (121 words) - 23:02, 14 March 2013
- This page was written by Jatin Luthra, a 2015 Google Code-in student, which explains how to install Apertium on Maegia872 bytes (125 words) - 02:58, 9 March 2018
- #REDIRECT [[Task ideas for Google Code-in/Add words from frequency list]]73 bytes (11 words) - 20:20, 13 November 2013
- ...pertium MT system: Wordbound blanks, developed during the Google Summer of Code 2020. = How to use wordbound blanks in the pipeline =313 bytes (42 words) - 18:58, 21 August 2020
- [[Category:Tasks for Google Code-in|Hand-correct spelling errors]]95 bytes (10 words) - 19:30, 16 November 2013
- Present your coding challenge in IRC or on the mailing list and ask [[Category:Ideas for Google Summer of Code]]681 bytes (107 words) - 15:27, 5 April 2021
- [[Category:Tasks for Google Code-in|Check output of word aligner]]96 bytes (12 words) - 20:40, 17 November 2013
- ...all the work done in the [[Kazakh and Sakha]] pair during Google Summer of Code 2018. The project consisted mainly of building a bilingual bidix and enrich2 KB (233 words) - 07:41, 14 August 2018
- This page was written by Jatin Luthra, a 2016 Google Code-in student, which explains how to install Apertium on FreeBSD595 bytes (84 words) - 02:55, 9 March 2018
