Search results

• 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
• 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
• 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
• 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
• 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
• Constraint-based lexical selection module
  '''apertium-lex-tools''' provides a module for compiling lexical selection rules and processing them in the pipeline. Rules can be manually ==Lexical transfer in the pipeline==
  19 KB (2,820 words) - 15:26, 11 April 2023
• Narimann/GSOC 2019 proposal: Kazakh-Turkish and Turkish-Kazakh
  * Write new transfer rules * Write constraint-based lexical selection
  8 KB (1,094 words) - 13:10, 14 April 2019
• Ideas for Google Summer of Code
  | rationale = Apertium-separable is a newish module to process lexical items with discontinguous dependencies, an area where Apertium has traditio ...n two existing language modules, focusing on the dictionary and structural transfer
  23 KB (3,198 words) - 09:15, 4 March 2024
• Testvoc
  ...it just expands an {{sc|sl}} dictionary, and runs each possibly analysed [[lexical form]] through all the translation stages to see that for each possible inp ...-quality language pair also needs testvoc on phrases consisting of several lexical units. Often one can find a lot of the errors by running a large corpus (wi
  9 KB (1,400 words) - 22:30, 18 January 2021
• Ideas for Google Summer of Code/Automatic blank handling
  ...formatting / superblanks interacts with word/chunk reordering in Apertium. Transfer rules can reorder words, but never look at the tags themselves, and have no ...in the input to a transfer rule are always output before the output that a transfer rule gives; so a <p> will never be moved around by a rule.
  8 KB (1,364 words) - 12:15, 14 May 2017
• English and Kazakh
  ** write lexical selection to generate "yesh-" forms from "any-" forms in negatives or "bir" ***lexical selection for "anything" as "yeshnarse" for negative sentences and as "bir
  20 KB (2,856 words) - 06:26, 27 May 2021
• Task ideas for Google Code-in
  |title=expand coverage of Kyrgyz to English structural transfer ...bilingual dictionary is not fully (or correctly) parsed by the <tt>kir-eng-transfer</tt> Apertium mode. Determine what rule(s) need(s) to be added (or fixed)
  32 KB (4,862 words) - 06:23, 5 December 2019
• Quick and dirty guide addendum: other important things
  === Lexical Selection === ...xt level of problem, once you've chosen the correct morphological form, is lexical selection. The sort of problem this best solves is when you have one stem
  10 KB (1,615 words) - 07:43, 20 December 2015
• The quick and dirty guide to making a new language pair
  ...rules is detected in the source language text, Apertium will follow these transfer rules to create a grammatical translation in the target language. If this works, great! We move on to the next section: The addition of transfer rules.
  19 KB (3,164 words) - 20:58, 2 April 2021
• How to figure out what's wrong with a translation
  Missing or incorrect Disambiguation and Lexical Selection rules often cause the wrong word to be translated. Problems in d === Lexical Selection ===
  5 KB (903 words) - 11:57, 26 September 2016

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