Search results
Jump to navigation
Jump to search
- ...od of around 12 years. The original <code>interNOSTRUM</code> was released in early 2000 and took around 72 person-months (four people, 18 months) to dev ...stry of Science, Industry and Commerce of the Spanish State to rewrite the code as open-source, and to convert the linguistic data. After one person year,12 KB (1,683 words) - 08:42, 10 May 2013
- ...od of around 12 years. The original <code>interNOSTRUM</code> was released in early 2000 and took around 72 person-months (four people, 18 months) to dev ...stry of Science, Industry and Commerce of the Spanish State to rewrite the code as open-source, and to convert the linguistic data. After one person year,12 KB (1,683 words) - 11:00, 30 October 2015
- ...od of around 12 years. The original <code>interNOSTRUM</code> was released in early 2000 and took around 72 person-months (four people, 18 months) to dev ...stry of Science, Industry and Commerce of the Spanish State to rewrite the code as open-source, and to convert the linguistic data. After one person year,12 KB (1,679 words) - 12:00, 31 January 2012
- Here are some top-tips for working with Apertium in the [[Google Code-in]]: ...GitHub] account. We use [[git]] and GitHub for collaboratively developing code.518 bytes (88 words) - 08:11, 16 September 2018
- ...e ([http://apertium.svn.sourceforge.net/viewvc/apertium/trunk/oooapertium/ code]) ...s the API of Google Translate: implemented as part of the Google Summer of Code 2009 projects, see [[Apertium services]]3 KB (451 words) - 19:20, 18 August 2014
- '''begiak''' is the IRC bot in the #apertium [[IRC]] channel. It serves several purposes, including to sho ...|sushain]], Qasim, and a number of other GCI students since then. The core code base is the [https://github.com/mutantmonkey/phenny mutantmonkey port] to P8 KB (1,234 words) - 17:01, 3 December 2020
- ...from current XML code. Morphtrans can of course be redesigned a bit, and, in fact, it should. ...onverts a <code>.mode</code> shell-script fragment into a <code>modes.xml</code> file.2 KB (324 words) - 11:37, 16 February 2016
- | Fill in gaps in formal docs ...to go from a word-order or agreement difference to a working transfer rule in either formalism6 KB (849 words) - 17:59, 25 March 2022
- * Capability in APY to bypass captcha code (for testing) * Finished suggestions feature in APY and html-tools3 KB (369 words) - 17:06, 1 July 2016
- ...s translation between two languages. It is one of the main five data files in any language pair (see also: [[Apertium New Language Pair HOWTO]]). ...ub]] (https://github.com/apertium). The bilingual dictionary file name are in the form ''apertium-A-B.A-B.dix'' where ''apertium-A-B'' is the name of the7 KB (1,244 words) - 16:41, 17 March 2018
- This is the ideas page for [[Google Summer of Code]], here you can find ideas on interesting projects that would make Apertium ...a, add your name to "Interested mentors" using <code><nowiki>~~~</nowiki></code>.23 KB (3,198 words) - 09:15, 4 March 2024
- ...of all the work done in the Romanian-Catalan pair during Google Summer of Code 2018. It also includes information on the upgrade of four language pairs wh ...monolingual package system and develop it to bring it to release quality. In addition, four other language pairs have been upgraded to the monolingual p7 KB (1,071 words) - 10:48, 14 August 2018
- ...s or phrases you find that are incorrectly translated, to getting involved in creating a new language pair or programming on tools or user interfaces. He ...en.wikipedia.org/wiki/C++ C++]. The various development helpers are mostly in [https://python.org/ Python].7 KB (1,139 words) - 06:27, 27 May 2021
- ...r translating from [[Tatar]] to [[Russian]]. The pair is currently located in [https://github.com/apertium/apertium-tat-rus GitHub]. ! Stems in the bilingual dictionary8 KB (1,006 words) - 12:48, 9 March 2018
- ...s or phrases you find that are incorrectly translated, to getting involved in creating a new language pair or programming on tools or user interfaces. ...e on the [[IRC|IRC channel]] <code>#apertium</code> on <code>irc.oftc.net</code>.3 KB (549 words) - 09:17, 26 May 2021
- ...h]] — [[Tatar]] || [[trunk]] || <code>kaz-tat</code>, <code>tat-kaz</code> || — || ~{{:Apertium-kaz-tat/stats/kaz-average}}%{{slc|kaz}}, ~{{:Aperti ...]] || [[Turkish]] — [[Crimean Tatar]] || [[trunk]] || <code>crh-tur</code> || - || - || {{#lst:Apertium-crh-tur/stats|crh-tur_stems}} || - || -6 KB (591 words) - 22:50, 30 October 2017
- * <code>translation lookup</code> turns on dictionary lookup mode. <code><pre>5 KB (712 words) - 21:27, 16 August 2016
- .../Tokenisation for spaceless orthographies]] being worked on [[User:Eiji]] in 2023 https://docs.google.com/document/d/1aTTGoLLCpr2gncq2FJIWG0InUH3tJ6epHxioKEDhNPs/edit?usp=sharin605 bytes (84 words) - 03:31, 14 July 2023
- This article will explain the basic process for completing a [[Google Code-in]] task. First, go to the [https://codein.withgoogle.com/tasks/ Google Code-in tasks page]. Next, open the "Organizations" drop-down and click the box nex444 bytes (73 words) - 02:31, 18 December 2019
- [[Lttoolbox-java|In English]] * Pendant le [[Google Summer of Code]] de 2009 [[User:Rah|Raphaël]] et [[User:Sortiz|Sergio]] ont travaillé de10 KB (1,597 words) - 13:07, 7 October 2014
