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
