Search results
Jump to navigation
Jump to search
Page title matches
- 6 KB (838 words) - 17:47, 25 July 2012
- 5 KB (620 words) - 12:21, 27 July 2012
Page text matches
- ...mmatical and other transformations between the two languages involved, and lexical data for the part-of-speech tagger, which is in charge of the disambiguatio ...nd keep only the bilingual data (lexical selection, bilingual transfer and transfer rules) in the "pair" directory.50 KB (7,915 words) - 00:04, 10 March 2019
- Writing transfer rules seems to be tricky. People generally understand the basic concepts, b ...ion in the target language morphological generator. This means that if the transfer needs some information about the available forms of a particular word, e.g.28 KB (4,478 words) - 12:25, 17 March 2022
- analysis of Apertium) and in the transfer and generation, the transducers from The design is based on the classic transfer architecture of machine translation,58 KB (8,964 words) - 11:11, 14 May 2016
- ...is, the dictionary is used in the direction Left/right. 'surface form' -> 'lexical unit'. ...('lemma') and tags for all matches (lemma and tags together are called a 'lexical unit').29 KB (4,687 words) - 16:28, 5 June 2020
- ...the initial developer. It is another developer, full beginner for writing transfer rules who chose to do that. The examples given are the first rules written ...ool ''apertium-transfer''. Writing tags used for [[chunking]] in a 3-stage transfer is not approached there.58 KB (8,365 words) - 20:16, 26 June 2018
- ...s with [[lexical selection]], for more information on the topic, see the [[lexical selection|main page]].'' the question of lexical selection becomes significant, because there11 KB (1,814 words) - 03:22, 9 March 2019
- ...is, and show how basic (that is, single level) morphological and syntactic transfer rules can be made in Apertium. ...atures they share, and how they are distinguished. When working on shallow-transfer machine translation, we can consider for example, both morphological contra16 KB (2,302 words) - 12:00, 31 January 2012
- ...is, and show how basic (that is, single level) morphological and syntactic transfer rules can be made in Apertium. ...atures they share, and how they are distinguished. When working on shallow-transfer machine translation, we can consider for example, both morphological contra16 KB (2,303 words) - 08:22, 10 May 2013
- ...is, and show how basic (that is, single level) morphological and syntactic transfer rules can be made in Apertium. ...atures they share, and how they are distinguished. When working on shallow-transfer machine translation, we can consider for example, both morphological contra16 KB (2,303 words) - 10:57, 30 October 2015
- There are two main issues with transfer in this case, the first is re-ordering, from <code>OVS → SVO</code>, the ...hat like the chunking available in Apertium (see [[Chunking]]), however no transfer takes place, it just groups words into chunks. The grammar is quite familia26 KB (4,167 words) - 13:05, 11 May 2016
- [[A long introduction to transfer rules|In English]] == Transfert lexical et transfert de structure ==27 KB (4,440 words) - 14:51, 7 October 2014
- ...ransfer module is necessary. This session describes the Apertium 3+ level transfer system which was designed to allow easier treatment of longer patterns, and ===Chunking-based transfer===14 KB (1,969 words) - 12:00, 31 January 2012
- ...ransfer module is necessary. This session describes the Apertium 3+ level transfer system which was designed to allow easier treatment of longer patterns, and ===Chunking-based transfer===14 KB (1,975 words) - 08:36, 10 May 2013
- ...ransfer module is necessary. This session describes the Apertium 3+ level transfer system which was designed to allow easier treatment of longer patterns, and ===Chunking-based transfer===14 KB (1,975 words) - 10:58, 30 October 2015
- ==Lexical transfer== The first stage of transfer is lexical transfer. This is where we take the tree that we have just constructed, and we trans53 KB (8,811 words) - 04:05, 21 January 2017
- ...and lexical selection. The theory section will cover some details of why a transfer lexicon (or bilingual dictionary) cannot always be just correspondences bet ...the second is marking in the entries features which need to be inferred by transfer rules. For example, choosing the most frequent translation of the Chuvash w13 KB (2,053 words) - 12:00, 31 January 2012
- ...and lexical selection. The theory section will cover some details of why a transfer lexicon (or bilingual dictionary) cannot always be just correspondences bet ...the second is marking in the entries features which need to be inferred by transfer rules. For example, choosing the most frequent translation of the Chuvash w13 KB (2,056 words) - 08:20, 10 May 2013
- ...and lexical selection. The theory section will cover some details of why a transfer lexicon (or bilingual dictionary) cannot always be just correspondences bet ...the second is marking in the entries features which need to be inferred by transfer rules. For example, choosing the most frequent translation of the Chuvash w13 KB (2,056 words) - 10:56, 30 October 2015
- ...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 i21 KB (3,171 words) - 14:34, 3 April 2017
- ...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
- ...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 t16 KB (2,285 words) - 06:46, 12 April 2019
- ===Transfer=== Transfer-based machine translation works by first converting the source language to12 KB (1,464 words) - 12:00, 31 January 2012
- ===Transfer=== Transfer-based machine translation works by first converting the source language to11 KB (1,519 words) - 06:51, 11 May 2013
- ===Transfer=== Transfer-based machine translation works by first converting the source language to11 KB (1,519 words) - 18:27, 16 October 2015
- ...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''' 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
- | [[Lexical form]] | [[Lexical unit]]13 KB (1,601 words) - 23:31, 23 July 2021
- !colspan="2"| lexical transfer !colspan="2"| lexical selection6 KB (873 words) - 14:35, 28 July 2020
- ...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
- ...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
- '''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
- * Write new transfer rules * Write constraint-based lexical selection8 KB (1,094 words) - 13:10, 14 April 2019
- | 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 transfer23 KB (3,198 words) - 09:15, 4 March 2024
- ...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 (wi9 KB (1,400 words) - 22:30, 18 January 2021
- ...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
- ** 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 "bir20 KB (2,856 words) - 06:26, 27 May 2021
- |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
- === 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 stem10 KB (1,615 words) - 07:43, 20 December 2015
- ...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
- 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
- Missing or incorrect Disambiguation and Lexical Selection rules often cause the wrong word to be translated. Problems in d === Lexical Selection ===6 KB (900 words) - 19:45, 2 December 2013
- ...transfer rule to an existing language pair and test that it works. [[/Add transfer rule|Read more]]... || [[User:Mlforcada]] [[User:ilnar.salimzyan]] [[User: ...selection quality of a pair and test them to ensure that they work. [[/Add lexical-select rules|Read more]]... || [[User:Mlforcada]], [[User:Francis Tyers]]68 KB (10,323 words) - 15:37, 25 October 2014
- * Write documentation on the current status of transfer rules * Write documentation on the current status of transfer rules5 KB (506 words) - 14:56, 28 August 2017
- ...s with [[lexical selection]], for more information on the topic, see the [[lexical selection|main page]].'' ...anguage or a constraint grammar it is possible to do '''limited rule-based lexical selection'''.7 KB (1,057 words) - 21:07, 1 December 2013
- ...e ''cantábamos'' would be <code>cantar.vblex.pii.p1.pl</code> (''cantar'', lexical verb, imperfect indicative, 1st person, plural). ...ode>pl.n.kitabu</code>, ''natural'' meaning that in this way, morphemes in lexical forms would be in the same order as in surface forms, and one could use thi6 KB (935 words) - 13:49, 21 August 2018
- ...khimova.pdf Study of the problem of creating structural transfer rules and lexical selection for the Kazakh-Russian machine translation system on Apertium pla ...ers/turklang2015-amirova.pdf Choosing the model for solving the problem of lexical selection for English-Kazakh language pair in the free/open-source platform33 KB (4,418 words) - 11:52, 29 December 2021
- ...an="6"| [[Helsinki Apertium Workshop/Session 4|4: Lexical transfer]] || '''Practical''': Dictionary work .../p/apertium/svn/branches/courses/helsinki_2013/slides/session4.pdf Lexical transfer]8 KB (720 words) - 15:18, 20 March 2015
- Based on a system of transfer rules and dictionaries written in markup language, Apertium is a platform t ...ng as a spell protractor, provided us with a consistent base data from the lexical point of view in the LSC and a valid model for the creation and assignment7 KB (1,110 words) - 11:34, 23 August 2016
- '''Transfer rules (English to Catalan):''' 221 (T1X), 60 (T2X), 38 (T3X) '''Transfer rules (Catalan to English):''' 97 (T1X), 28 (T2X), 9 (T3X)7 KB (973 words) - 21:38, 9 May 2018
- ==Transfer== There are 51 structural transfer rules that take Crimean Tatar constructions and turn them into their Turkis4 KB (551 words) - 23:52, 28 August 2017
