Search results
Jump to navigation
Jump to search
Page title matches
- * 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
- This task is almost done, see -r59428 and -r57945 in apy SVN. * _e in mode names turns into underlined e in the dropdown, should just be _e4 KB (652 words) - 12:52, 26 March 2015
- ...you can take to get involved with the Apertium project in the Google Code-in. First of all, thanks for reading! We're very enthusiastic about getting ne ...o hang out on IRC, even if no-one is talking when you enter. People can be in different time zones, and channel activity peaks depending on the time.7 KB (1,091 words) - 19:54, 12 April 2021
- (Second draft in by [[User:Francis Tyers|Francis Tyers]] 15:34, 28 October 2013 (UTC)) ...ation engine and auxiliary tools is being developed around the world, both in universities and companies (e.g. Prompsit Language Engineering) and by a gr6 KB (1,057 words) - 15:34, 28 October 2013
- The objective of these tasks is to write code to intersect two finite-state transducers. One transducer is a [[morphologi ...the set of strings in the morphological dictionary which have translations in the bilingual dictionary.5 KB (798 words) - 14:01, 17 March 2020
- See our '''[[Task ideas for Google Code-in/Getting started|Getting started guide]]''' if you're a current GCI student! See our '''[[Task ideas for Google Code-in/Mentor guidelines|Mentor guidelines]]''' if you're an Apertium GCI mentor o3 KB (412 words) - 22:18, 24 December 2019
- ;Why does your organisation want to participate in Google Code-in 2016? ...that focuses a lot on marginalised languages. GCI gives us a chance to get in touch with the next generation of speakers, and to show them how they can h3 KB (516 words) - 21:03, 29 October 2016
- * Sites with scholarly articles: Google Scholar, jstor, academia.edu, etc. [[Category:Tasks_for_Google_Code-in|Documentation of resources]]1 KB (202 words) - 19:55, 12 April 2021
- ...s page for Google Code-In 2012 (http://www.google-melange.com/gci/homepage/google/gci2012), here you can find ideas on interesting tasks that will improve yo '''For current GCI task ideas, see [[Task ideas for Google Code-in]]'''14 KB (2,007 words) - 03:06, 27 October 2013
- #REDIRECT [[Task ideas for Google Code-in/Add words from frequency list]]73 bytes (11 words) - 20:20, 13 November 2013
- Words can have more than one possible interpretation, for example, "tie" in English can be a noun denoting an item of clothing "she put on her tie" or ...That is, for each ambiguous word you choose the appropriate interpretation in context.3 KB (574 words) - 16:30, 11 January 2020
- ...North Sámi–Norwegian Bokmål and Kazakh–Tatar among others), and many more in development. ;Why would you organisation like to participate in Google Code-in 2015?*7 KB (1,111 words) - 10:10, 15 November 2015
- You must evaluate each sentence in three ways: # Fluency (0-5): How well-formed is the target sentence in the target language.478 bytes (73 words) - 19:56, 12 April 2021
- ...errors (the translation is not adequate because the part-of-speech tagger in Apertium has selected the wrong morphological analysis for a word that had ...nd write 5 constraint grammar rules that select the desired part of speech in the relevant context(s);1 KB (193 words) - 14:27, 29 October 2013
- The objective of this task is to take (or make) a dictionary in text format and extract the ''paradigm sketches'' from it. By this we mean ...them into word categories. The suffixes and categories should be described in the dictionary.2 KB (151 words) - 23:20, 14 November 2013
- ...m but no reasonable bilingual dictionary (these language pairs are usually in the incubator), for instance apertium-spa-pol ...most frequent unknown words''' (words in the source document which are not in the bilingual dictionaries of the language pair). See below for informatio2 KB (320 words) - 15:01, 19 January 2020
- And a list in a file (filename given as the first argument to the script) like ...ement. Also, note how :yaa<n> does not comment out the line that has "yaa" in its <l> element.3 KB (576 words) - 12:57, 2 January 2016
- <spectre> URL: https://svn.code.sf.net/p/apertium/svn/trunk/lttoolbox/lttoolbox/lt_print.cc <spectre> URL: https://svn.code.sf.net/p/apertium/svn/trunk/lttoolbox/lttoolbox/transducer.cc2 KB (247 words) - 19:56, 12 April 2021
- ...rors''' (the translation is not adequate because the part-of-speech tagger in Apertium has selected the wrong morphological analysis for a word that had ...rite 10 constraint grammar rules''' that select the desired part of speech in the relevant context(s);1 KB (156 words) - 02:19, 21 October 2018
- [[Category:Tasks for Google Code-in|Hand-correct spelling errors]]95 bytes (10 words) - 19:30, 16 November 2013
Page text matches
- == Why is it you are interested in machine translation? == ...n" in which the MT is an intermediate step in the production of a document in the TL, which will be published. To facilitate this process, it is usual to21 KB (3,171 words) - 14:34, 3 April 2017
- ...nality mirroring that of Apertium's "lt-proc", but which loads transducers in the formats supported by HFST. The lookup tool tokenises the input text on ...ictionary entries, and some rules. Some rules have been worked on, but are in an incomplete state.16 KB (2,571 words) - 12:21, 20 June 2019
- ...n computer code, or takes input and output in forms very close to computer code. ...uter coding. How much you need to know depends on your interests. Building in Apertium needs an interest and an enthusiasm for languages, and a will to e17 KB (2,835 words) - 16:16, 24 January 2017
- http://google-melange.appspot.com/gci/homepage/google/gci2011 ==Что это такое, Google Code-In ?==56 KB (2,087 words) - 19:57, 12 April 2021
- ;Why does your organisation want to participate in Google Code-in 2018? ...that focuses a lot on marginalised languages. GCI gives us a chance to get in touch with the next generation of speakers, and to show them how they can h3 KB (443 words) - 11:20, 11 September 2018
- Here are the main tips to help you in writing your GSOC application with Apertium. ...still interested, but we'll try to find a subset of it which is achievable in the time scale available.9 KB (1,509 words) - 23:51, 27 February 2023
- ;Why does your organisation want to participate in Google Code-in 2016? ...that focuses a lot on marginalised languages. GCI gives us a chance to get in touch with the next generation of speakers, and to show them how they can h3 KB (516 words) - 21:03, 29 October 2016
- ...iteria selection criteria], and [http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors advice for mentors] Fill out the application form [http://code.google.com/soc/2008/org_signup.html here].8 KB (1,255 words) - 19:50, 12 April 2021
- ...you can take to get involved with the Apertium project in the Google Code-in. First of all, thanks for reading! We're very enthusiastic about getting ne ...o hang out on IRC, even if no-one is talking when you enter. People can be in different time zones, and channel activity peaks depending on the time.7 KB (1,091 words) - 19:54, 12 April 2021
- ...on engine and auxiliary tools is being developed around the world, largely in universities and companies (e.g. Prompsit Language Engineering), but also i ...ton—French, and Basque—Spanish among others), and several more in development.13 KB (2,013 words) - 12:21, 20 June 2019
- ; Why does your org want to participate in Google Summer of Code? ...ution of existing developers through mentoring and to improve the platform in many ways: improving the engine, generating new tools and user interfaces,5 KB (833 words) - 15:49, 11 January 2018
- ...on engine and auxiliary tools is being developed around the world, largely in universities and companies (e.g. Prompsit Language Engineering), but also i ...ton—French, and Basque—Spanish among others), and several more in development.11 KB (1,802 words) - 19:51, 12 April 2021
- See our '''[[Task ideas for Google Code-in/Getting started|Getting started guide]]''' if you're a current GCI student! See our '''[[Task ideas for Google Code-in/Mentor guidelines|Mentor guidelines]]''' if you're an Apertium GCI mentor o3 KB (412 words) - 22:18, 24 December 2019
- ; Why does your organisation want to participate in Google Code-in 2017? ...that focuses a lot on marginalised languages. GCI gives us a chance to get in touch with the next generation of speakers, and to show them how they can h2 KB (421 words) - 15:37, 10 October 2017
- apertium-nn-nb is now in a fairly usable state for translating both ending in -lig in nb typically end in -leg in nn) and checking whether12 KB (1,886 words) - 12:20, 20 June 2019
- 2. svn co https://svn.code.sf.net/p/apertium/svn/trunk/apertium-dan-nor The language pair was developed as part of Google Summer of Code 2013 by [http://www.linkedin.com/pub/jonas-fromseier-mortensen/45/69/839 Jo21 KB (3,367 words) - 15:17, 27 October 2013
- ...tails about Apertium in the [https://code.google.com/soc/ Google Summer of Code] (GSOC). ...putational linguistics or any combination of the above, then [[contact|get in touch]].6 KB (674 words) - 14:52, 19 January 2023
- ankushgupta@students.iiit.ac.in<br /> == Interest in Machine Translation ==6 KB (923 words) - 17:57, 3 April 2010
- ** especially relevant for Google Code-in * committing without a net connection / on an airplane / in a boat4 KB (547 words) - 08:06, 30 January 2015
- Turkish - intermediate(5 years of studying in Kazakh-Turkish school) == Why is it that you are interested in Apertium? ==8 KB (1,094 words) - 13:10, 14 April 2019
