Search results

• Ideas for Google Summer of Code/Add a new variety to an existing language
  * 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
• Roadmap
  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
• Ideas for Google Summer of Code/Visual interface to write structural transfer rules
  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, intui
  1 KB (162 words) - 01:11, 18 August 2015
• Task ideas for Google Code-in/Setup and add lexical selection
  ...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
• Task ideas for Google Code-in/Lemmatise words from frequency list
  ...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
• Ideas for Google Summer of Code/Apertium in chat clients
  * 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
• Tatar and Bashkir/GSOC 2018
  ...://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 we
  2 KB (262 words) - 13:17, 14 August 2018
• Ideas for Google Summer of Code/Spell checker web interface
  ...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
• Prerequisites for FreeBSD
  This page was written by Jatin Luthra, a 2016 Google Code-in student, which explains how to install Apertium on FreeBSD
  595 bytes (84 words) - 02:55, 9 March 2018
• Ideas for Google Summer of Code/Improve integration of lttoolbox in libvoikko
  * Writing a method for <code>liblttoolbox</code> which would allow analysis of a string as opposed to a file stream. [[Category:Ideas for Google Summer of Code|Improve integration of lttoolbox in libvoikko]]
  932 bytes (130 words) - 14:22, 29 February 2012
• Ideas for Google Summer of Code/Improving support for non-standard text input
  * Propose ways in which they might be solved. [[Category:Ideas for Google Summer of Code|Improving support for non-standard text input]]
  902 bytes (121 words) - 12:50, 10 March 2014
• Ideas for Google Summer of Code/Closer integration with HFST
  * Fix [https://sourceforge.net/p/hfst/bugs/153/ this bug] in <code>hfst-proc</code> tokenisation. * Make <code>hfst-expand</code> obey flag diacritics.
  1 KB (170 words) - 23:58, 5 April 2013
• Ideas for Google Summer of Code/Unify the metadix formats
  * Write a XSLT sheet that transforms as many entries <e> as possible in the standard section of the dictionary as follows: [[Category:Ideas for Google Summer of Code|Unify the metadix formats]]
  1 KB (243 words) - 11:47, 14 February 2014
• Ideas for Google Summer of Code/Rule-based finite-state disambiguation
  ...e transducer. It might be a good idea to express this as constraint rules, in a novel XML-based file format. ...rocessor (see [[Apertium stream format]]) for the output of <code>lt-proc</code> that parses character by character, respecting [[superblanks]].
  2 KB (237 words) - 00:53, 24 March 2013
• Bilingual dictionary discovery
  You could make a graph out of these dictionaries where each node is a word in a language, and each arc is a language pair. For example like: http://i.img * [[Ideas for Google Summer of Code/Improved bilingual dictionary induction]]
  3 KB (487 words) - 00:02, 22 March 2018
• Indonesian and Malaysian/Work plan
  ...orts for the [[Indonesian and Malaysian]] translator in [[Google Summer of Code]] 2012. ...| <code><ij> <cnjcoo> <cnjsub> <cnjadv> <det> <pr> <num> <prn> <np> <adv></code>|| ||
  3 KB (402 words) - 17:05, 22 August 2012
• Task ideas for Google Code-in/Unigram tagger
  [[Category:Tasks for Google Code-in|Unigram tagger]]
  255 bytes (43 words) - 14:56, 26 October 2014
• Gci task ideas
  #REDIRECT [[Task ideas for Google Code-in]]
  43 bytes (6 words) - 07:49, 27 November 2015
• Google Summer of Code/Report 2014
  * [[Plugins#In progress]] [[Category:Google Summer of Code|Report 2014]]
  3 KB (305 words) - 08:31, 13 January 2015
• Uzbek
  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

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)