Search results

Jump to navigation Jump to search

Page title matches

Page text matches

  • Contributing to an existing pair
    ...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
  • A long introduction to transfer rules
    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
  • Documentation of Matxin 1.0
    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
  • Workflow reference
    ...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
  • Transfer rules examples
    ...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
  • Lextor
    ...s with [[lexical selection]], for more information on the topic, see the [[lexical selection|main page]].'' the question of lexical selection becomes significant, because there
    11 KB (1,814 words) - 03:22, 9 March 2019
  • Курсы машинного перевода для языков России/Session 5
    ...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 contra
    16 KB (2,302 words) - 12:00, 31 January 2012
  • Helsinki Apertium Workshop/Session 5
    ...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 contra
    16 KB (2,303 words) - 08:22, 10 May 2013
  • Tartu Apertium Course/Session 5
    ...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 contra
    16 KB (2,303 words) - 10:57, 30 October 2015
  • Matxin 1.0 New Language Pair HOWTO
    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 familia
    26 KB (4,167 words) - 13:05, 11 May 2016
  • Introduction aux règles de transfert
    [[A long introduction to transfer rules|In English]] == Transfert lexical et transfert de structure ==
    27 KB (4,440 words) - 14:51, 7 October 2014
  • Tartu Apertium Course/Session 6
    ...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
  • Курсы машинного перевода для языков России/Session 6
    ...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
  • Helsinki Apertium Workshop/Session 6
    ...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
  • Matxin New Language Pair HOWTO
    ==Lexical transfer== The first stage of transfer is lexical transfer. This is where we take the tree that we have just constructed, and we trans
    53 KB (8,811 words) - 04:05, 21 January 2017
  • Курсы машинного перевода для языков России/Session 4
    ...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 w
    13 KB (2,053 words) - 12:00, 31 January 2012
  • Helsinki Apertium Workshop/Session 4
    ...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 w
    13 KB (2,056 words) - 08:20, 10 May 2013
  • Tartu Apertium Course/Session 4
    ...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 w
    13 KB (2,056 words) - 10:56, 30 October 2015
  • 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
  • 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
  • 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 &lt;p&gt; 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
  • Как узнать почему перевод неправильный
    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
  • Task ideas for Google Code-in (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
  • English and Catalan/Workplan
    * Write documentation on the current status of transfer rules * Write documentation on the current status of transfer rules
    5 KB (506 words) - 14:56, 28 August 2017
  • Limited rule-based lexical selection
    ...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
  • Prefixes and infixes
    ...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 thi
    6 KB (935 words) - 13:49, 21 August 2018
  • Helsinki Apertium Workshop/Programme
    ...an="6"| &nbsp; [[Helsinki Apertium Workshop/Session 4|4:&nbsp;Lexical&nbsp;transfer]] || &nbsp; '''Practical''': Dictionary work .../p/apertium/svn/branches/courses/helsinki_2013/slides/session4.pdf Lexical transfer]
    8 KB (720 words) - 15:18, 20 March 2015
  • Publications
    ...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 platform
    33 KB (4,418 words) - 11:52, 29 December 2021
  • Sardinian and Italian/Final Report
    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 assignment
    7 KB (1,110 words) - 11:34, 23 August 2016
  • English and Catalan
    '''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
  • Crimean Tatar and Turkish/GSoC Report
    ==Transfer== There are 51 structural transfer rules that take Crimean Tatar constructions and turn them into their Turkis
    4 KB (551 words) - 23:52, 28 August 2017
  • Kiel aldoni novan lingvoparon
    ...por substantivoj. Transiraj regulaj dosieroj havas siajn proprajn DTD-on (transfer.dtd) kiujn oni povas trovi en la Apertium-a enpako. Se vi bezonas krei regu <transfer>
    34 KB (5,392 words) - 07:13, 16 February 2015
  • Layouts
    ....af-en.t1x || Afrikaans&mdash;English first stage transfer file (transfer) |apertium-en-af.af-en.t2x || Afrikaans&mdash;English second stage transfer file (interchunk)
    5 KB (583 words) - 11:17, 18 November 2013
  • Multiwords
    #* <pre>after disambiguation and pre-transfer: ^coffee# with milk<n><sg>$</pre> #* <pre>after disambiguation and pre-transfer: ^coffee# with milk<n><pl>$</pre>
    21 KB (3,521 words) - 05:17, 10 December 2017
  • Norwegian Nynorsk and Norwegian Bokmål/arkiv
    For no er dette gjort med ein spesiell kategori ngen_time_meas i transfer; sidan regelen for ngen_time_meas kjem først i fila, prøver me ikkje meir ...practical problems come when trying to integrate this with disambiguation, transfer and generation in Apertium.
    13 KB (2,051 words) - 10:24, 22 September 2010
  • Ambiguity
    * word-sense / lexical selection ambiguity ==Word-Sense / Lexical Selection ambiguity==
    4 KB (620 words) - 18:06, 26 September 2016
  • Apertium stream format
    ...s should only appear escaped in the input stream unless they are part of a lexical unit, chunk or superblank. ...e characters <code>^</code> and <code>$</code> are reserved for delimiting lexical units
    6 KB (797 words) - 07:12, 29 March 2022
  • Chunking: A full example
    First a little overview of how 3-stage transfer normally works: * Transfer stage: Words are translated using the bidix and categorized and put into ch
    15 KB (2,237 words) - 12:41, 21 August 2015
  • VM for transfer
    .../sub> &rarr; ^(lexical_unit)$ || Pops 'N' values from the stack, creates a lexical unit ^...$ with them and pushes the lu back onto the stack | lu-count || - || N/A || [empty] &rarr; number || Pushes the number of lexical units (words inside the chunk) in the rule onto the stack
    14 KB (2,020 words) - 13:58, 7 October 2014
  • Linguistic issues for North Saami to Inari Saami machine translation
    === [[sme-smn sátneválljen|Sátneválljen (Lexical selection)]] === === [[Errors in the North Saami transfer component|Transfer]] ===
    3 KB (557 words) - 12:11, 31 March 2017
  • Generating lexical-selection rules from monolingual corpora
    This page describes how to generate lexical selection rules without relying on a parallel corpus. *** <code>-multi</code> which is all the modules after lexical transfer (see apertium-mk-en/modes.xml)
    12 KB (1,634 words) - 18:26, 26 September 2016
  • Task ideas for Google Code-in (2012)
    ...ds. For further information, you can consult the [[How to get started with lexical selection rules|getting started guide]]. || [[User:Francis Tyers|Francis Ty ...ies to a transfer lexicon of your choice. This will involve adding lexical transfer entries, which consist of a translation, and its corresponding grammatical
    14 KB (2,007 words) - 03:06, 27 October 2013
  • Курсы машинного перевода для языков России/Session 7
    .... Consider the following example: we can see that for each source language lexical form, there is a corresponding entry in the bilingual dictionary. ...ode>#</code> mark errors in the lexical transfer, and in the morphological transfer/generation respectively.
    18 KB (2,490 words) - 12:00, 31 January 2012
  • Helsinki Apertium Workshop/Session 7
    .... Consider the following example: we can see that for each source language lexical form, there is a corresponding entry in the bilingual dictionary. ...ode>#</code> mark errors in the lexical transfer, and in the morphological transfer/generation respectively.
    18 KB (2,493 words) - 08:39, 10 May 2013
  • Tartu Apertium Course/Session 7
    .... Consider the following example: we can see that for each source language lexical form, there is a corresponding entry in the bilingual dictionary. ...ode>#</code> mark errors in the lexical transfer, and in the morphological transfer/generation respectively.
    18 KB (2,493 words) - 10:59, 30 October 2015
  • Uighur and Turkish/GSoC2018 report
    ...uages. The project consisted mainly of building a bilingual bidix, writing transfer and disambiguation rules and enriching the Uyghur morphological analyzer. ==Transfer==
    5 KB (607 words) - 13:25, 12 August 2018
  • Apertium separable
    ==Lexical transfer in the pipeline== ...to apply to input. Also, it will need to be able to handle the output of transfer. —[[User:Firespeaker|Firespeaker]] ([[User talk:Firespeaker|talk]]) 00:0
    15 KB (2,420 words) - 18:54, 2 May 2024
  • Basque and Spanish
    ...s (plural-ergative) so that no election is made until the word reaches the transfer module. But this would cause that the morphological analysis is not complet ...te forms unless a def-mult element is defined in the tagger with 2 or more lexical forms.
    11 KB (1,758 words) - 13:22, 10 December 2010
  • Sevel ur c'houblad yezhoù nevez
    ...uzkas evit an anvioù-kadarn. Restroù DTD eo ar restroù reolennoù treuzkas (transfer.dtd) a c'haller kaout e pakad Apertium. Mar fell deoc'h enplementañ ur reo <transfer>
    35 KB (5,602 words) - 07:14, 16 February 2015
  • Siciliano y castellano/Informe final
    ...ags and words with different lexical meanings based on the grammatical and lexical context. CG rules work both for disambiguation within one part of speech an The rules of '''lexical selection''' are needed when one word has different meaning depending on it
    9 KB (1,370 words) - 13:58, 23 August 2016
  • Ideas for Google Summer of Code/Weighted transfer rules
    At the moment Apertium transfer rules are combinations of fixed-length patterns and actions. Conflicts are Transfer rules:
    5 KB (804 words) - 11:54, 9 March 2017
  • English and Catalan/GSOC 2017
    ===Transfer rules=== ...fferent transfer stages, and the code is quite convoluted. Work related to transfer rules has focused on code updates to ensure everything is applied correctly
    5 KB (887 words) - 22:24, 31 August 2017
  • Ideas for Google Summer of Code/lint for Apertium
    .... A lint tester would help people write standard code for dictionaries and transfer files. ...ol should at least check [[lttoolbox]] (dix) dictionary data, perhaps also transfer rules. The [[Apertium New Language Pair HOWTO]] should introduce most of th
    5 KB (789 words) - 10:36, 31 May 2016
  • Apertium-recursive/Formalism
    This states that if a lexical unit has a target-language <code><mf></code> tag and a rule tries to replac ==== Literal Lexical Units ====
    32 KB (5,012 words) - 13:27, 6 September 2023
  • Tartu Apertium Course
    ..."|Friday<br/>(6th October) || 10:00 &mdash; 12:00 || Lexical transfer | 14:00 &mdash; 18:00 || Lexical transfer
    3 KB (329 words) - 19:16, 13 November 2015
  • Apertium cat-srd and ita-srd/GSoC 2017
    ===Lexical selection rules=== The translator has 274 lexical selection rules. These are rules that choose between two or more possible t
    9 KB (1,306 words) - 15:56, 2 September 2017
  • English and Kazakh/Pending tests
    # fix tags of "be" in transfer # transfer rules to get tags from beAdjVerb to new be{{tag|v}}
    8 KB (741 words) - 03:41, 4 September 2017
  • Cascaded Interchunk
    ...rchunk (see "advanced transfer" in the official documentation). Interchunk transfer uses 3 steps and cascaded interchunk uses more than 3. *Then, the chunks are formed by reading lexical forms left-to-right and building the longest-matching sequence that matches
    4 KB (669 words) - 14:12, 6 July 2012
  • Turkic MT Improvements GSoC2019 report
    ...ach language pair. After that the focus was on tur-uig and uzb-tur. CG and transfer rules were written to improve the translation quality for these languages. ==Transfer==
    7 KB (798 words) - 18:30, 26 August 2019
  • Machine translation with Constraint Grammar
    ===Lexical=== You can use some other system for lexical transfer (e.g. an Apertium bilingual dictionary), or you can do it directly in CG.
    3 KB (368 words) - 11:35, 26 August 2011
  • Apertium-kaz-kir/Workplan
    * A couple easy lexical selection rules are still not written. # write ≥4 lexical selection rules
    8 KB (975 words) - 06:42, 23 September 2013
  • Translation Rules and Difficulties (English & Chinese)
    ===Lexical Selection Errors（因词害义）=== ...". However, "干" is also colloquial slang for "f***". The translator's poor lexical selection resulted in a widely-circulated internet joke.
    12 KB (1,637 words) - 16:03, 21 January 2016
  • Recursive transfer
    * Do we try and find syntactic relations in the transfer, or do we pre-annotate (e.g. with CG) then use the tags from CG to constrai ...allow for >1 possible TL translation ? to allow 'lexical selection' inside transfer as well as outside ?
    5 KB (788 words) - 10:50, 9 February 2015
  • Ces-Rus/Workplan
    ...lexical selection. Work on rudimentary transfer rules, as well as begin on transfer rules for verbs. | Continue work on transfer rules for verbs.
    4 KB (521 words) - 05:48, 5 June 2017
  • Conjoined lexical units
    ...face form can correspond to multiple lexical units. When this happens, the lexical units are connected with <code>+</code>. ...hin the same <code>^…$</code> in the output of the analyser), while during transfer they are considered separate (a single <code>+</code> will give two <code>^
    4 KB (654 words) - 08:31, 6 April 2021
  • Uputstvo za novi jezički par za Apertium
    ...otrebna su nam pravila prevoda za imenice. Pravila prevoda imaju svoj DTD (transfer.dtd), koji se može naći u paketu Apertiuma. Ako treba da implementirate p <transfer>
    26 KB (4,259 words) - 07:00, 16 February 2015
  • Infrastructure discussion
    :* Transfer (syntactic + lexical) ...ule-based) and the ability to move around chunks (NP, V, etc.) rather than lexical units.
    3 KB (406 words) - 14:29, 13 April 2008
  • Google Summer of Code/Report 2013
    ===Improvements in lexical-selection module=== * [[User:Fpetkovski/GSOC 2013 Application - Improving the lexical selection module]]
    2 KB (200 words) - 08:21, 13 January 2015
  • Modes
    * -lex runs up until lexical selection * -transfer runs up until (1-stage) transfer
    6 KB (824 words) - 22:30, 24 January 2022
  • Lttoolbox-java
    * Execute transfer stages (all 3 of them) ...the C++ binaries for preparing/developing a language pair, i.a. to compile transfer files and train the tagger.
    9 KB (1,370 words) - 09:49, 7 April 2020
  • Compounds
    ...c compounding magic for generation – transfer should simply output several lexical units in a row with no spaces between them. We typically use a (non-hidden) Example: after transfer we might have <code>^krans<n><m><sg><ind><cmp>$^kake<n><f><sg><ind>$</code>
    16 KB (2,689 words) - 09:07, 6 April 2021
  • Learning rules from parallel and non-parallel corpora
    ...ce is available. This section describes several (3) methods for estimating lexical selection rules using a parallel corpus. We start by describing the part of ...-tagger-output</code> and the [[Lexical selection module scripts reference|lexical selection scripts]]. (The program [[multitrans]] should be installed by ape
    14 KB (2,181 words) - 19:01, 17 August 2018
  • Dependency based re-ordering
    ...r during transfer) based on the dependency tree (this would not do lexical transfer, concordance or anything else, just LU reordering). The sister project [[Ma ...nvert <code>cg-proc</code> to output dependency information along with the lexical units. The second stage would be to write a module that builds a tree and d
    6 KB (804 words) - 08:44, 3 October 2013
  • Google Summer of Code/Report 2009
    I had to write the transfer rules from scratch, but this also went Apertium documentation; nn-nb uses only one-stage transfer since the
    12 KB (1,886 words) - 12:20, 20 June 2019
  • Chinese and Spanish
    ...oped the analysis dictionary, the bilingual dictonary, the three levels of transfer rules. ===Transfer rules===
    7 KB (830 words) - 21:33, 30 September 2013
  • Preparing to use apertium-transfer-tools
    ...has an [http://apertium.svn.sourceforge.net/viewvc/apertium/trunk/apertium-transfer-tools/example/ example] directory in the source package, which should be th apertium-transfer:
    6 KB (1,022 words) - 08:15, 8 October 2014
  • Why we trim
    ...s from the analyser will have some match in the bidix, and all output from transfer will have some entry in the generator.<ref>Typically this goes for both tra ...certain nouns, and gender is not even present in the source language. The transfer rule expects to have this information; without it, not only will the noun b
    4 KB (679 words) - 16:06, 3 May 2020
  • Adyghe and Russian
    Lexical transfer: Lexical selection:
    6 KB (412 words) - 23:31, 31 January 2020
  • List of symbols
    | <code>vblex</code> || Standard ("lexical") verb || ''see also: vbser, vbhaver, vbmod, vaux, vbdo'' || VERB | <code>&lt;r></code> || Right side (lexical unit) || In <code>&lt;p></code>. Ex.: <code><r>beer&lt;s n="noun"/>&
    38 KB (4,492 words) - 15:36, 9 May 2024
  • Modes introduction
    | apertium-transfer -n '/home/shane/apertium/en-es/apertium-en-es/apertium-en-es.en-es.genitive | apertium-transfer -b '/home/shane/apertium/en-es/apertium-en-es/apertium-en-es.en-es.t1x' '/
    6 KB (992 words) - 17:25, 22 September 2016
  • Retrospective: Google Code-In 2017
    <li> "Add 200 words to the bilingual dictionary" or "Add 1 lexical transfer rule" </li> <li> "Add 500 words to the bilingual dictionary" or "Add 10 lexical transfer rules" or "Write a constrastive grammar" or ... </li>
    10 KB (1,668 words) - 02:46, 10 February 2018
  • Automated extraction of lexical resources
    Some ideas for (semi-)automatically extracting lexical resources from # Transfer rules
    6 KB (928 words) - 13:57, 3 April 2009
  • Lexical selection in target language
    ...s with [[lexical selection]], for more information on the topic, see the [[lexical selection|main page]].'' ...-multiple-translations it is possible to get an ambiguous text output from transfer, it comes in the following form:
    4 KB (596 words) - 21:06, 1 December 2013
  • Apertium going SOA
    ...mong different languages and systems within the biomedical domain. MetaMap Transfer (MMTx) is a Java program that makes MetaMap available to biomedical researc ...temporairly switching (until I find a proper solution) to Boost::Spirit, a lexical scanner and parser generator that is already in service's dependencies (it'
    24 KB (3,572 words) - 07:37, 8 March 2018
  • Generating lexical-selection rules from a parallel corpus
    If you have a parallel corpus, one of the things you can do is generate some lexical selection rules from it, to improve translation of words with more than one See [[Constraint-based lexical selection module]] for apertium-lex-tools.
    15 KB (2,206 words) - 13:58, 7 October 2014
  • Cómo Contribuir a un par de lenguas existentes
    ...o de las reglas de *transfert estructural) llama el módulo de *transfert *lexical (generado a marchar del diccionario bilingüe) colgando todo el proceso par ...almente leer la *DTD del fichero de las reglas de *transfert estructural (*transfer.*dtd) Proporcionada con el lote de *Apertium, en el cual todos los elemento
    53 KB (8,542 words) - 10:15, 14 January 2008
  • Ideas for Google Summer of Code/superblank handling algorithm
    ...s may necessitate a change in the lexical form formats that the structural transfer modules deal with. * What happens if new words are added by a structural transfer rule? What should they be equipped with?
    9 KB (1,486 words) - 19:56, 24 March 2020
  • Google Season of Docs 2022/Organize and Update Apertium User Documentation
    | Transfer tutorials * How to go from a word-order or agreement difference to a working transfer rule in either formalism
    6 KB (849 words) - 17:59, 25 March 2022
  • Ideas for Google Summer of Code/Add weights to lttoolbox
    # lexical transfer ## lexical selection
    5 KB (816 words) - 02:32, 13 February 2018
  • Surface forms in the pipe
    ...hrown away after the tagger. It might be handy to be able to keep it until transfer in order to be able to substitute things unknown to the bidix. ...<tt>word2vec</tt> to be used in the tagger and lexical selection modules. Lexical selection could also potentially use surface forms too.
    4 KB (715 words) - 22:51, 26 June 2020
  • Placeholder attributes
    ...shows that there is a decision to be made in the transfer rules where the lexical information of the word doesn't directly allow a decision to be made. ...module. These tags must be changed into these others in the output of the transfer module:
    2 KB (334 words) - 07:45, 8 October 2014
  • Comment contribuer à une paire de langues existante
    ...ichier des règles de transfert structurel) appelle le module de transfert lexical (généré à partir du dictionnaire bilingue) pendant tout le processus po ...ouvez également lire la DTD du fichier des règles de transfert structurel (transfer.dtd) fournie avec le paquet Apertium, dans lequel tous les éléments du la
    54 KB (8,480 words) - 18:55, 10 April 2017
  • Hindi and Bengali
    ...'s coverage to cover more words of the languages. We also need to add more transfer rules to cover all the [https://wiki.apertium.org/wiki/Hindi_and_Bengali/Pe * <s>Hin > Ben transfer rules on nouns, verbs tenses and adj added.</s>
    4 KB (557 words) - 05:45, 25 August 2021
  • Documentation
    ...cal selection/disambiguation is covered, but this is now replaced by the [[Lexical selection]] module. * [[Preparing to use apertium-transfer-tools]]
    5 KB (599 words) - 19:04, 17 February 2020
  • Руководство по созданию новой языковой пары
    ...я существительных. Файлы с правилами трансфера имеют свой собственный DTD (transfer.dtd), который может быть найден в пакете Apert <transfer>
    56 KB (1,826 words) - 17:48, 13 April 2019
  • North Saami and Finnish/Pending tests
    ::Tra should transfer to Ess by default. ===Lexical selection===
    10 KB (1,492 words) - 07:13, 10 December 2015
  • Apertium Turkic
    ...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 platform
    13 KB (1,710 words) - 20:32, 30 August 2018
  • Semantic tagging
    biltrans and before lexical selection. It would essentially reweight And pass it to the lexical selection module which will choose the
    5 KB (949 words) - 15:27, 15 June 2020
  • Як створити нову мовну пару
    ...ансферу для іменників. Файли з правилами трансферу мають свій власний DTD (transfer.dtd), який може бути знайдений в пакеті Apertiu <transfer>
    54 KB (1,909 words) - 21:01, 2 April 2021
  • Leipzig workshop
    # Lexical Transfer # Lexical Selection
    929 bytes (110 words) - 09:22, 27 July 2018
  • Bosnian-Croatian-Montenegrin-Serbian and Slovenian/TODOs for the article
    * work on lexical selection examples for the same (Filip) * transfer, and transfer examples in both directions (Hrvoje)
    2 KB (223 words) - 15:58, 23 April 2013
  • Polish and Russian/Project description
    '''Constraint grammar and transfer rules''' ...ags and words with different lexical meanings based on the grammatical and lexical context. CG rules work both for disambiguation within one part of speech an
    4 KB (570 words) - 18:43, 23 August 2016
  • Syntactic labels
    ...ng verb phrase co-ordinators from noun phrase co-ordinators lets you write transfer rules to merge two co-ordinated NPs. ...ysis, even implementing part of it can prove useful in writing transfer or lexical selection rules.
    7 KB (922 words) - 08:16, 8 October 2014
  • Ideas for Google Summer of Code/Corpus-based lexicalised feature transfer
    ...a module that sits somewhere in the Apertium pipeline (somewhere after the lexical selection and before morphological generation) that sets features (e.g. tag ...d as definite. One way of dealing with this is a lot of rules and lists in transfer, but those are hard to do. So, how about looking at a corpus for informatio
    2 KB (262 words) - 11:19, 9 February 2015
  • Kazakh and Tatar/TODO
    ...coverage, CG performance, regression and pending tests targeted mainly at transfer rules, a “gold standard” parallel corpus to measure the WER and to alwa * transfer
    4 KB (603 words) - 21:20, 31 August 2015
  • Exemples de règles de transfert
    [[Transfer rules examples|In English]]
    60 KB (8,894 words) - 21:10, 20 November 2019
  • Helsinki Apertium Workshop
    ...ednesday<br/>(15th January) || 09:00 &mdash; 13:00 || Lexical transfer | 14:00 &mdash; 17:00 || Structural transfer
    2 KB (182 words) - 12:46, 9 May 2013
  • Kurmanji and English/Final report
    ...orked on adding vocabulary, disambiguation rules in CG, transfer rules and lexical selection. ! Transfer
    2 KB (335 words) - 10:29, 23 August 2016
  • Weighted transfer rules
    https://svn.code.sf.net/p/apertium/svn/branches/weighted-transfer/ ...nsfer module from https://svn.code.sf.net/p/apertium/svn/branches/weighted-transfer/apertium/.
    11 KB (1,215 words) - 14:43, 17 April 2018
  • Ideas for Google Summer of Code/Backpropagation
    * If you have the right words in the wrong order, that's probably transfer * If the correct word was present after bidix but not after lexical selection, that's the issue
    1 KB (220 words) - 14:54, 3 February 2021
  • Dialectal or standard variation
    This may look like a lexical selection problem to be handled by difference. Before the lexical selection stage we run the CG-file
    14 KB (2,355 words) - 10:33, 1 November 2022
  • North Saami and South Saami
    * [[North Saami - South Saami lexical selection]] * [[North Saami - South Saami quasicode for the transfer files]]
    859 bytes (115 words) - 13:23, 5 January 2016
  • Kyrgyz and Kazakh
    * [[Constraint-based lexical selection module|apertium-lex-tools]] ...az-kir.dix</code>, lexical selection is in the <code>.lrx</code> file, and transfer rules are in the <code>.t1x</code> and <code>.t2x</code> files.
    3 KB (304 words) - 01:51, 10 March 2018
  • Ideas for Google Summer of Code/Apertium FST CG
    ...erms of syntax to other Apertium modules (dictionaries, lexical selection, transfer rules, etc). The [[Constraint-based lexical selection module]] could be used as reference implementation, as it handles
    1 KB (234 words) - 19:48, 24 March 2020
  • Letter case handling
    The same input word in a lexical processing module can be written differently regarding letter case. The mo ...less it is decided not to do so. The case can be changed in the structural transfer module; this option is useful, for example, when there is a reordering of w
    5 KB (801 words) - 07:13, 8 October 2014
  • Initial consonant mutation
    ...useful for this purpose as it cannot look at surface forms of words, only lexical units. A trivial illustrative example of how the constraint grammar can be * <code>apertium-ga-gd.pre-<math>x</math>.t1x</code> &mdash; Transfer rules which add tags defining the mutation to the beginning of words which
    6 KB (1,000 words) - 07:12, 8 October 2014
  • Constructions
    ...ike syntactic transfer, most of them have probably have some kind of fixed lexical element. ...re not easy to translate word-for-word, but also quite annoying to have in transfer rules.
    1 KB (207 words) - 07:51, 9 October 2014
  • Google Summer of Code/Application 2019
    To transfer to the application ...ine translation system, which uses finite state transducers for all of its lexical transformations, and hidden Markov models and/or constraint grammars for pa
    8 KB (1,230 words) - 06:02, 5 February 2019
  • Google Summer of Code/Application 2020
    To transfer to the application ...ine translation system, which uses finite state transducers for all of its lexical transformations, and hidden Markov models and/or constraint grammars for pa
    8 KB (1,248 words) - 15:51, 17 February 2021
  • Ideas for Google Summer of Code/Add a new variety to an existing language
    ...es). This will involve working with dictionaries, lexical selection rules, transfer rules, scripting, corpora. The objective is to facilitate the generation of ** Add all the words, and cover all the structures with transfer rules.
    2 KB (377 words) - 19:18, 25 January 2023
  • Apertium-recursive/Bytecode
    Recursive transfer bytecode files are written using <code>Lttoolbox/compression.h</code>. The ...code>boolean</code>, and <code>Chunk</code>, where Chunk objects represent lexical units, chunks, and blanks.
    10 KB (1,387 words) - 06:09, 1 June 2023
  • ReTraTos
    ...resources useful for machine translation (MT): bilingual dictionaries and transfer rules. The induction systems and open linguistic data can be used with the In order to use ReTraTos, the surface forms of each lexical unit need to be re-added so that the above example looks like the following
    8 KB (1,273 words) - 09:32, 3 May 2024
  • Tagger training
    You can also write lexical rules, so for example in Afrikaans, the word "deur" is ambiguous, one meani (Clarification: it only works with ''one-stage transfer'', so Apertium 3 pairs which only have t1x can still use it.)
    7 KB (1,058 words) - 07:37, 4 July 2016
  • Capitalization restoration
    ...tionary case and there is no need to track the proper placement of case in transfer. The format of the CRX rules is modeled after the [[Constraint-based lexical selection|LRX]] format.
    7 KB (1,042 words) - 19:44, 4 March 2024
  • Google Summer of Code/Wrap-up Report 2009
    ...ical analyser / generator] for Bengali and a substantial amount of lexical transfer, so the project was a great success.
    12 KB (1,917 words) - 15:54, 12 September 2009
  • Bengali and English/Transfer Postchunk
    ''Comment'' : just transfer the lexical unit
    323 bytes (27 words) - 16:41, 15 August 2011
  • Building a pseudo-parallel corpus
    ...to-multitrans.py to expand the biltrans sentence to cover all the possible lexical transfers. You can also use apertium-lex-tools/scripts/biltrans-to-multitra * Run through the rest of the pipeline from apertium-transfer -b onwards to get target-language sentences
    3 KB (364 words) - 23:25, 23 August 2012
  • Apertium-kaz-kir/TODO
    ** Add lexical selection rules and transfer rules as needed
    2 KB (243 words) - 21:22, 19 August 2015
  • Tatar and Russian
    |lexical selection||rowspan="2" | adding stems & cleaning testvoc |colspan="4" style="text-align:center"| transfer rules for pending wiki tests (focus on phrases and clauses, not single word
    8 KB (1,006 words) - 12:48, 9 March 2018
  • North Saami and South Saami/Regression tests
    ..." leamen, then put the Ind+Prs+Sg3 og the werb of "vååjnedh" og "govledh" (Lexical. Selection) ...tjie gonnoeh aehtjieh". aahka gonnoeh aajjah, tjidtjie gonnoeh aehtjieh = (Transfer Rule) Altså i de ordene som har konjunksjonen "gonnoeh" skal ha det siste
    26 KB (3,823 words) - 21:01, 13 April 2020
  • File names
    * XXX-YYY.autolex.bin :: the compiled [[Lexical selection]] rule file, in direction from language XXX to language YYY * XXX-YYY.t1x.bin :: the compiled transfer rules (stage 1 / chunking, or the only stage if no chunking used) when tran
    890 bytes (126 words) - 10:10, 14 March 2017
  • Meta-evaluation
    ** Number of lexical selection rules ** Number of transfer rules
    2 KB (246 words) - 02:32, 1 June 2019
  • Google Summer of Code/Application 2021
    ...ine translation system, which uses finite state transducers for all of its lexical transformations, and hidden Markov models and/or constraint grammars for pa
    10 KB (1,480 words) - 07:00, 23 February 2021
  • List of Apertium mentors
    ...ches to morphological analysis and disambiguation, dependency grammars and lexical selection. ...Emailuser/Popcorndude|email]]) || popcorndude || '''English''', Español || Transfer, documentation, rule learning || Undergrad at Swarthmore college studying l
    9 KB (1,164 words) - 15:01, 1 April 2021
Retrieved from "https://wiki.apertium.org/wiki/Special:Search"