Search results

• User:Aida/Application
  ...chine translation is very important, because Kazakh is Turkic language, so transfer, constraint grammar rules, which I write for this pair can be useful for de ...e 2013. I have great experience in writing and correcting transfer rules, lexical selection and constraint grammar rules, also adding vocabulary in monolingu
  7 KB (1,078 words) - 05:24, 13 May 2014
• Grfro3d/proposal apertium cat-srd and ita-srd
  ...as dictionaries, bilingual dictionaries, grammars and rules and structural transfer files. RBMT systems consist of an engine (coding and decoding), data (lingu ...with possessives, proclitics, enclitics, ordinals, superlatives, etc.) and lexical selection. It would be better to spend more time on apertium cat>srd that i
  21 KB (3,171 words) - 14:34, 3 April 2017
• User:Aboelhamd/proposal
  '''GSOC 2019 : Extend weighted transfer rules'''[http://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code#Exte ...) to apertium , and that encouraged me to choose the idea "Extend weighted transfer rules" to continue our work, extend, integrate and deploy the full module.
  18 KB (2,903 words) - 22:18, 8 April 2019
• User:Pmodi/GSOC 2020 proposal: Hindi-Punjabi
  ...for both languages, the hin-pan bilingual dictionary and writing suitable transfer rules to bring this pair to a releasable state. * Lexical selection and transfer rules for the pair
  27 KB (4,091 words) - 19:32, 4 June 2020
• Northern Sámi and Norwegian
  ...on and lexical selection, and [[lttoolbox]]/apertium modules for the rest. Transfer is four-stage [[chunking]]. The pipeline looks like this: pretransfer | lt-proc (lexical transfer) | cg-proc (lexical selection) |\
  16 KB (2,604 words) - 19:42, 17 April 2018
• Hectoralos/GSOC 2019 proposal: Catalan-Italian and Catalan-Portuguese
  ...n the dictionaries, introduce lexical selection rules and create some more transfer rules, a low WER can be reached. ...guese, but also for Italian) and the introduction of a few more structural transfer rules. In any case, I am totally open to suggestions and will be happy to t
  16 KB (2,285 words) - 06:46, 12 April 2019
• Курсы машинного перевода для языков России/Session 0
  ===Transfer=== Transfer-based machine translation works by first converting the source language to
  12 KB (1,464 words) - 12:00, 31 January 2012
• Helsinki Apertium Workshop/Session 0
  ===Transfer=== Transfer-based machine translation works by first converting the source language to
  11 KB (1,519 words) - 06:51, 11 May 2013
• Tartu Apertium Course/Session 0
  ===Transfer=== Transfer-based machine translation works by first converting the source language to
  11 KB (1,519 words) - 18:27, 16 October 2015
• User:SilentFlame/updatedPipeline
  ===transfer (chunker)=== * Make hfst-proc correctly disperse inline blanks onto each lexical unit until the next <code><nowiki>[</nowiki></code>
  9 KB (1,217 words) - 08:02, 4 September 2017
• Apertium New Language Pair HOWTO
  ...do full syntactic parsing, the rules are typically operations on groups of lexical units, rather than operations on parse trees. ...ent of gender, number, etc. The rules can also be used to insert or delete lexical items, as will be described later. These files are:
  36 KB (5,933 words) - 16:14, 22 February 2021
• User:Khannatanmai/New Apertium stream format
  ...we are going to modify all the parsers to include the surface form in the lexical unit, in our discussion(can be found on the discussion page) we concluded t ...rbitrary information in each lexical unit, such as markups, and hence when lexical units get moved around, the markups don't move with them.
  24 KB (4,167 words) - 09:20, 17 July 2020
• User:Aidana/Proposal
  ...irection. I am planning to expand the dictionary, create more transfer and lexical rules. ...it could produce translation with high quality, bigger vocabulary and more transfer rules. Resources could be used for another language pairs, where the Kazakh
  9 KB (1,088 words) - 19:28, 24 March 2016
• Lexical selection
  '''Lexical selection''' is the task of choosing, given several source-language (SL) tr This page has some links to pages about lexical selection in Apertium.
  4 KB (625 words) - 08:36, 29 April 2015
• User:Rroychoudhury/GSoC 2020 Proposal
  ...languages I am most familiar with , and it would be interesting to develop transfer rules for building a bridge between the two so that people can utilise this ...tion to this I wish to incorporate some changes in the disambiguation and lexical selection step. Below are the details of what I propose to introduce.
  16 KB (2,215 words) - 14:49, 31 March 2020
• Traductions en français
  | [[Lexical form]] | [[Lexical unit]]
  13 KB (1,601 words) - 23:31, 23 July 2021
• Apertium system architecture
  !colspan="2"| lexical transfer !colspan="2"| lexical selection
  6 KB (873 words) - 14:35, 28 July 2020
• Talk:Chuvash and Turkish
  * Lexical selection: ҫителӗклӗ vs самай * Lexical selection: кил vs. ҫурт
  15 KB (1,093 words) - 17:36, 4 May 2012
• Anaphora resolution module
  ...he [[pipeline]]: In the '''Anaphora Resolution module''' and the in the '''Transfer''' stage. ...or in the Anaphora Resolution module and select the correct pronoun in the Transfer stage.
  20 KB (3,107 words) - 21:13, 24 June 2022
• Weighted transfer rules at GSoC 2016
  ...age for [[Ideas_for_Google_Summer_of_Code/Weighted_transfer_rules|Weighted transfer rules project]] conducted by [[User:Nikita Medyankin|Nikita Medyankin]] at ...e takes exclusive precedence and blocks out all its ambiguous peers during transfer precompilation stage.
  9 KB (1,387 words) - 13:37, 23 August 2016

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