Apertium has moved from SourceForge to GitHub.
If you have any questions, please come and talk to us on #apertium on irc.freenode.net or contact the GitHub migration team.

Search results

Jump to navigation Jump to search

There is a page named "Transfer rules" on this wiki. See also the other search results found.

Page title matches

  • Some pointers to useful Wiki pages for writing transfer rules: * [[A long introduction to transfer rules]]
    520 bytes (44 words) - 17:12, 20 December 2016
  • ...[Ideas_for_Google_Summer_of_Code/Weighted_transfer_rules|Weighted transfer rules project]] conducted by [[User:Nikita Medyankin|Nikita Medyankin]] at Google ...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
  • 14 KB (1,120 words) - 12:59, 28 November 2018
  • This page provides general documentation on the transfer rules used in the English-Catalan pair. The tables are generated from the data an |Adds 'més' before an adjective in comparative or superlative form (for rules with two adjectives).
    45 KB (7,840 words) - 10:56, 18 September 2017
  • 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
  • Writing transfer rules seems to be tricky. People generally understand the basic concepts, but the * There are no recursive rules. Rules match fixed-length patterns. There is no optionality at the level of words.
    25 KB (3,981 words) - 11:56, 16 May 2020
  • ...of this task is to allow rules to conflict and to select the most adequate rules for an input using weights. ; Lexicalised rules weights: Depend on one or more of the lemmas of the input words. e.g.
    5 KB (804 words) - 11:54, 9 March 2017
  • ==Transfer rules German->Danish== ===Single word rules German->Danish===
    2 KB (351 words) - 18:50, 30 October 2016
  • Apertium structural transfer rules are currently encoded in XML-based formats. These are very overt and clear, ...rrent XML-based language, allows for a graphical, intuitive editing of the rules, and writes compilable .t1x, .t2x or .t3x files)
    1 KB (162 words) - 01:11, 18 August 2015
  • ...ting transfer rules who chose to do that. The examples given are the first rules written to translate a group of one, two or three Esperanto words into a gr ...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
  • This page provides general documentation on the transfer rules used in the Romanian-Catalan pair. The tables are generated from the data a === Extra transfer (T4X) ===
    14 KB (1,989 words) - 10:06, 28 November 2018

Page text matches

  • ...bytecode transfer gives exactly the same result''' as the old interpreted transfer, down to the handling of wrong clip statements (but excluding invoking macr ....svn.sourceforge.net/viewvc/apertium/trunk/lttoolbox-java/src/org/apertium/transfer/development/FindAndCompareAllReleasedTransferFiles.java?revision=20387&view
    67 KB (9,057 words) - 06:52, 24 September 2013
  • 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
  • Writing transfer rules seems to be tricky. People generally understand the basic concepts, but the * There are no recursive rules. Rules match fixed-length patterns. There is no optionality at the level of words.
    25 KB (3,981 words) - 11:56, 16 May 2020
  • ...ting transfer rules who chose to do that. The examples given are the first rules written to translate a group of one, two or three Esperanto words into a gr ...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
  • ...clude mainly dictionaries (monolingual and bilingual), structural transfer rules that perform grammatical and other transformations between the two language ...nly the bilingual data (lexical selection, bilingual transfer and transfer rules) in the "pair" directory.
    50 KB (7,915 words) - 00:04, 10 March 2019
  • ...s of interesting grammatical features that we're going to use to write the rules. First we define some part-of-speech and morphological tags, e.g. After we've defined our terms, next come the rules, in the first section we're going to map the relations to the words in the
    53 KB (8,811 words) - 04:05, 21 January 2017
  • ...how 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
  • ...how 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
  • ...how 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
  • ...MT, but also to be able to intervene on the code to modify and change the rules. ...attiva.it/uri-res/N2Ls?urn:nir:stato:costituzione:1947-12-27!vig=.*], and "Rules on protection of historical linguistic minorities" [http://www.camera.it/pa
    21 KB (3,171 words) - 14:34, 3 April 2017
  • ...trange rules and also rules that may not be correct. Try to understand the rules we have. * Make sure all new rules have the correct superblank management
    20 KB (2,857 words) - 18:04, 8 March 2018
  • ===Transfer=== ...from this representation using both bilingual dictionaries and grammatical rules.
    12 KB (1,464 words) - 12:00, 31 January 2012
  • ===Transfer=== ...from this representation using both bilingual dictionaries and grammatical rules.
    11 KB (1,519 words) - 06:51, 11 May 2013
  • ===Transfer=== ...from this representation using both bilingual dictionaries and grammatical rules.
    11 KB (1,519 words) - 18:27, 16 October 2015
  • ...data. The data consists, on a basic level, of three dictionaries and a few rules (to deal with word re-ordering and other grammatical stuff). ...ished from deep-transfer in that it doesn't do full syntactic parsing, the rules are typically operations on groups of lexical units, rather than operations
    36 KB (5,936 words) - 13:12, 10 May 2020
  • ...stvoc clean -- it is missing some dictionary entries, and some rules. Some rules have been worked on, but are in an incomplete state. ...ysers for Czech and Polish, along with a lot of manual work. Some transfer rules were added for different phenomena between Polish and Czech.
    16 KB (2,571 words) - 12:21, 20 June 2019
  • There are two main issues with transfer in this case, the first is re-ordering, from <code>OVS → SVO</code>, the ...or word-category disambiguation and for specifying chunking and dependency rules. There are two more stages that come before morphological analysis, tokenis
    26 KB (4,167 words) - 13:05, 11 May 2016
  • ...[Ideas_for_Google_Summer_of_Code/Weighted_transfer_rules|Weighted transfer rules project]] conducted by [[User:Nikita Medyankin|Nikita Medyankin]] at Google ...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
  • ===Lexical transfer/Translation/bidex lookup=== This tool runs the bilingual dictionary transfer,
    29 KB (4,687 words) - 16:33, 19 January 2017
  • ...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
  • ...tionaries, introduce lexical selection rules and create some more transfer rules, a low WER can be reached. ...t 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 try new
    16 KB (2,285 words) - 06:46, 12 April 2019
  • ...data. The data consists, on a basic level, of three dictionaries and a few rules (to deal with word re-ordering and other grammatical stuff). ...detected in the source language text, Apertium will follow these transfer rules to create a grammatical translation in the target language.
    19 KB (3,175 words) - 17:33, 27 April 2017
  • ...translation quality. This will involve working with dictionaries, transfer rules, scripting, corpora. The objective is to make an Apertium language pair sta ...fied in a declarative language &mdash; and possibly [[Constraint Grammar]] rules if that is relevant)
    29 KB (4,112 words) - 19:54, 29 March 2020
  • ===Transfer rules=== ...nking rules after being partially rewritten. In addition, basic interchunk rules have been added, allowing gender and number match between noun/pronoun and
    7 KB (1,071 words) - 10:48, 14 August 2018
  • * 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
  • * Write new transfer rules * Write transfer rules (Turkish > Kazakh)
    8 KB (1,094 words) - 13:10, 14 April 2019
  • ...th the bilingual dictionary. At the same time, I would be writing transfer rules to ensure the release of the pair. Creating some basic rules for the transfer between Hindi (an Indo-Aryan language) and Telugu (a Dravidian language) wo
    9 KB (1,391 words) - 16:41, 31 March 2020
  • * dix-mode, for XML dictionary and transfer editing == XML (dix, transfer, …) editing ==
    16 KB (2,691 words) - 13:40, 20 November 2018
  • ...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.
    18 KB (2,808 words) - 12:12, 25 February 2020
  • ...ry and bilingual dictionary were created from scratch. Some basic transfer rules were added, the rest is left for the future work. ...dn't find any source for import. It was left to the future and now we have transfer rule for this case.
    5 KB (703 words) - 21:42, 22 August 2016
  • ...of this task is to allow rules to conflict and to select the most adequate rules for an input using weights. ; Lexicalised rules weights: Depend on one or more of the lemmas of the input words. e.g.
    5 KB (804 words) - 11:54, 9 March 2017
  • [[A long introduction to transfer rules|In English]] À ce point il vaut mieux ne pas confondre les rôles du [[lexical transfer|transfert lexical]] et du transfert de structure. Il y a une zone commune e
    27 KB (4,440 words) - 14:51, 7 October 2014
  • ...transfer rules were added according to the contrastive grammar (Some basic rules were added, the rest is left for the FUTURE). Additional work has been made ...- further changes were needed in the bilingual dictionary and in transfer rules because Spanish does not have perf/imperf form.
    7 KB (1,100 words) - 20:29, 30 August 2011
  • ===Transfer rules=== ...ransfer stages, and the code is quite convoluted. Work related to transfer rules has focused on code updates to ensure everything is applied correctly and s
    5 KB (887 words) - 22:24, 31 August 2017
  • ...fix and will require changes to both the transfer engine and the transfer rules. ...rmatter and re-formatter are generated from a format specification in XML. Rules for format, like linguistic data, are specified in XML, and they contain re
    13 KB (1,781 words) - 09:49, 6 October 2014
  • |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
  • '''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
  • ...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
  • * Fix transfer rules that didn't work as expected * Rewrite ron-cat transfer rules to use chunking
    5 KB (577 words) - 10:56, 14 August 2018
  • ...kes exclusive precedence and blocks out all its ambiguous peers during the transfer precompilation stage, often leading to inaccurate translation. ...uous rules. This way, if a specific pattern matches with multiple transfer rules, the rule with the largest weight for that pattern is applied.
    9 KB (1,322 words) - 13:19, 17 May 2019
  • However, as transfer rules may introduce errors that are not visible when translating single lexical u ...ransfer rules can refer to not only tags, but lemmas; and that multi-stage transfer means you have to test fairly long sequences.
    9 KB (1,350 words) - 13:37, 30 November 2018
  • ...g / superblanks interacts with word/chunk reordering in Apertium. Transfer rules can reorder words, but never look at the tags themselves, and have no gener ...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
  • ...th that and unfortunately with very few resources available. Currently the transfer system is in its primitive state and we are looking forward to complete the ...looking forward to increase the coverage alongside completing the transfer rules.
    4 KB (651 words) - 23:00, 26 August 2011
  • ...s and a bilingual package for Spanish-Sicilian equivalents and translation rules. ...ifferent lexical meanings based on the grammatical and lexical context. CG rules work both for disambiguation within one part of speech and between words of
    9 KB (1,370 words) - 13:58, 23 August 2016
  • ...for compiling lexical selection rules and processing them in the pipeline. Rules can be manually written, or learnt from monolingual or parallel corpora. ==Lexical transfer in the pipeline==
    9 KB (1,329 words) - 15:53, 1 March 2020
  • ...h points you've been able to handle (through the implementation of various rules—see below) and which points remain unhandled. To disambiguate these readings, you need to make rules based on the grammatical context. E.g., if the next word is a verb, then y
    10 KB (1,615 words) - 07:43, 20 December 2015
  • | 4 || 4 junh&mdash;10 junh || Adding words<br/>Transfer rules fra > oci || ~16,000 || ~89.0% || || || || 16745 ...iverable #1: French to Occitan translator</b> || Adding words<br/>Transfer rules fra > oci || <b>~18,000</b> || <b>~89.5%</b> || <b>~25%</b> ||
    4 KB (434 words) - 10:44, 9 August 2018
  • ...omuna) makes it necessary to opt for a machine translation system based on rules. Based on a system of transfer rules and dictionaries written in markup language, Apertium is a platform that is
    7 KB (1,110 words) - 11:34, 23 August 2016
  • ...formation, you can consult the [[How to get started with lexical selection rules|getting started guide]]. || [[User:Francis Tyers|Francis Tyers]] ...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
  • ....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
  • ...ely. Rules can be written in a format almost identical to that of apertium-transfer or in a somewhat [[Apertium-recursive/Formalism|Yacc-like]] format created <program name="apertium-transfer -b">
    7 KB (1,005 words) - 20:14, 12 January 2020
  • ...ang2015-rakhimova.pdf Study of the problem of creating structural transfer rules and lexical selection for the Kazakh-Russian machine translation system on ...pertium-turklang-2015-papers/turklang2015-karibayeva.pdf Lexical selection rules for Kazakh-to-English machine translation in the free/open-source platform
    30 KB (4,122 words) - 19:08, 17 February 2020
  • ...|| &nbsp;15:00&mdash;17:00&nbsp; || &nbsp; '''Practical''': Writing rules for morphological disambiguation ...an="6"| &nbsp; [[Helsinki Apertium Workshop/Session 4|4:&nbsp;Lexical&nbsp;transfer]] || &nbsp; '''Practical''': Dictionary work
    8 KB (720 words) - 15:18, 20 March 2015
  • ==apertium-transfer-tools== Automatic shallow-transfer rules generation from parallel corpora
    4 KB (525 words) - 19:21, 17 September 2009
  • 15 new morphological disambiguation rules for Catalan have been written and a few more have been modified. ===Lexical selection rules===
    9 KB (1,306 words) - 15:56, 2 September 2017
  • 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
  • ...build a prototype for this revered language pair in the future. Technical rules and definitions are left in their Chinese forms to assist any future Chines ...output. In Apertium terms, this is the result of wrong structural transfer rules.
    12 KB (1,637 words) - 16:03, 21 January 2016
  • ...r some mwe's), so after bidix has transferred "bekjempet" to "kjempa_mot", transfer needs to turn this into "kjempa(lemh) ofte<adv> mot(lemq)". This looks a bi ...><pres>$ ^ikkje<adv>$ ^*Jurafjella$ ^til<part><sep>$ ^*Alpane$' | apertium-transfer -n apertium-nn-nb.multiwords.t1x multiwords.bin
    23 KB (3,692 words) - 16:33, 27 August 2019
  • Missing or incorrect Disambiguation and Lexical Selection rules often cause the wrong word to be translated. Problems in disambiguation ca To disambiguate these readings, you need to make rules based on the grammatical context. E.g., if the next word is a verb, then y
    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: ...ty of a pair and test them to ensure that they work. [[/Add lexical-select rules|Read more]]... || [[User:Mlforcada]], [[User:Francis Tyers]] [[User:ilnar.
    68 KB (10,323 words) - 15:37, 25 October 2014
  • Missing or incorrect Disambiguation and Lexical Selection rules often cause the wrong word to be translated. Problems in disambiguation ca To disambiguate these readings, you need to make rules based on the grammatical context. E.g., if the next word is a verb, then y
    5 KB (903 words) - 11:57, 26 September 2016
  • Improving the existing English to Hindi wordlist and transfer rules available in Apertium. Apertium is a shallow-transfer machine translation system. Currently , at http://www.apertium.org/ no Indi
    6 KB (923 words) - 17:57, 3 April 2010
  • ...election. 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
  • ...and lexical selection. The theory section will cover some details of why a transfer lexicon (or bilingual dictionary) cannot always be just correspondences bet ...d is marking in the entries features which need to be inferred by transfer rules. For example, choosing the most frequent translation of the Chuvash word ''
    13 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 ...d is marking in the entries features which need to be inferred by transfer rules. For example, choosing the most frequent translation of the Chuvash word ''
    13 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 ...d is marking in the entries features which need to be inferred by transfer rules. For example, choosing the most frequent translation of the Chuvash word ''
    13 KB (2,056 words) - 10:56, 30 October 2015
  • #* <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
  • ! Transfer goal | Good coverage, insufficient CG rules
    3 KB (288 words) - 08:30, 23 July 2018
  • *The file with the transfer rules to be used (trules.xml or .t1x file &mdash; e.g. <code>apertium-oc-ca.oc-ca ===Extract regex rules===
    11 KB (1,470 words) - 08:16, 8 October 2014
  • ...nter | ---- || This section establishes the type of code generated and the transfer stage. ...ern is matched,<br /> we need to process all the patterns which are in the rules section.
    14 KB (2,020 words) - 13:58, 7 October 2014
  • ...dule to replace the apertium-transfer module(s) which will parse and allow transfer operations on an input. # Propose a transfer rule formalism
    2 KB (307 words) - 19:16, 28 February 2019
  • morf.analysis | morf.disambiguation | bidix | lexical selection | structural transfer | morf. generation * [[Learning rules from parallel and non-parallel corpora]]
    4 KB (625 words) - 08:36, 29 April 2015
  • [[Transfer rules examples|In English]]
    60 KB (8,894 words) - 21:10, 20 November 2019
  • ...analysis dictionary, the bilingual dictonary, the three levels of transfer rules. ===Transfer rules===
    7 KB (830 words) - 21:33, 30 September 2013
  • ...C]</ref> for adding closed-category terms and learning about morphological rules in general. ===Transfer rules===
    7 KB (1,063 words) - 11:13, 26 August 2011
  • ...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
  • ...age 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
  • 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
  • | [[A long introduction to transfer rules]] | [[Preparing to use apertium-transfer-tools]]
    13 KB (1,600 words) - 16:33, 27 April 2017
  • ...r for Serbo-Croatian, a bilingual dictionary, as well as a set of transfer rules. Since Serbo-Croatian entails several standard languages, we added correspo ...eve, be greatly improved by restructuring and reformulating of some of the rules. Also we have barelly tapped it's power regarding functional tags, so I thi
    8 KB (1,205 words) - 13:15, 28 August 2011
  • ==Transfer rules English->Esperanto== ===Single word rules English->Esperanto===
    7 KB (1,105 words) - 01:18, 4 February 2009
  • ** these markings again triggers certain transfer rules, most of them in the chunker ([http://apertium.svn.sourceforge.net/viewvc/a * To transfer from one part of speech to another
    5 KB (984 words) - 09:44, 24 August 2012
  • !colspan="2"| lexical transfer !colspan="2"| pre-transfer
    5 KB (793 words) - 23:00, 18 May 2020
  • {{deprecated2|Learning rules from parallel and non-parallel corpora}} ...el 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 possible transl
    15 KB (2,206 words) - 13:58, 7 October 2014
  • == Estimating rules using parallel corpora == ...his section describes several (3) methods for estimating lexical selection rules using a parallel corpus. We start by describing the part of the training pr
    14 KB (2,181 words) - 19:01, 17 August 2018
  • ...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
  • ** Implicit glue rules ...sure that we never get <code>Syntax error</code> (e.g. really robust glue rules).
    5 KB (788 words) - 10:50, 9 February 2015
  • ===Transfer rules=== ...ith some rules which are working very well. Still in my plans to build new rules and revise existing ones.
    5 KB (680 words) - 07:14, 26 August 2011
  • ;Transfer rules ==Transfer rules==
    7 KB (883 words) - 05:34, 22 August 2017
  • ...xisting rules in Apertium's pl-cs system originated in pl-sk. Take the new rules in pl-cs and apply them to pl-sk. No knowledge of Polish, Slovakian, or Cze ...module for the released pair and find out how many dictionary entries and rules it has. Put this into a spreadsheet and email the mailing list. Why? Our re
    187 KB (21,006 words) - 22:14, 12 November 2012
  • * Incorrect transfer direction. ==Transfer==
    8 KB (1,443 words) - 13:46, 18 August 2016
  • The idea of '''n-Stage transfer''' is to extend the <code>apertium-interchunk</code> so that it can "merge" The current chunk-based transfer would normally chunk this into:
    7 KB (1,079 words) - 13:58, 7 October 2014
  • 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
  • ==Shallow transfer == Shallow transfer means there is no parse trees (which are used in "deep transfer").
    4 KB (584 words) - 06:55, 8 October 2014
  • * A couple easy lexical selection rules are still not written. # write ≥4 lexical selection rules
    8 KB (975 words) - 06:42, 23 September 2013
  • === A Simple Set of Rules === !!! Tag rewrite rules
    33 KB (6,245 words) - 16:59, 9 January 2020
  • ...r lexical selection that works on statistics and rules, using the Apertium transfer language or a constraint grammar it is possible to do '''limited rule-based The general idea is that you use a transfer before transfer to add tags after the part-of-speech to differentiate between different tra
    7 KB (1,057 words) - 21:07, 1 December 2013
  • ==Transfer rules German->Danish== ===Single word rules German->Danish===
    2 KB (351 words) - 18:50, 30 October 2016
  • # Constraint rules (sensible ones) # Transfer rules
    6 KB (928 words) - 13:57, 3 April 2009
  • Case tags would need to be removed using appropriate transfer rules. This difference in word order would need to be dealt with in transfer rules.
    5 KB (783 words) - 02:36, 16 December 2016
  • ...orphological generator for the target language. Lexical units added in the transfer stage should also have entries in the target language generator. This must ...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
  • ...orphological generator for the target language. Lexical units added in the transfer stage should also have entries in the target language generator. This must ...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
  • ...orphological generator for the target language. Lexical units added in the transfer stage should also have entries in the target language generator. This must ...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
  • ==Derivations: general rules and exceptions== Sámi has a lot of derivation rules. There are various strategies used for translating these:
    10 KB (1,676 words) - 10:53, 16 April 2015
  • ...when there are ''unknown'' proper nouns in the input. One is that transfer rules that work on &lt;np&gt;-tagged words do not apply when the word is unknown. ==Unknown proper nouns in transfer==
    3 KB (492 words) - 16:52, 10 March 2018
  • ...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
  • Some pointers to useful Wiki pages for writing transfer rules: * [[A long introduction to transfer rules]]
    520 bytes (44 words) - 17:12, 20 December 2016
  • Applying forbid and enforce rules... Applying forbid and enforce rules...
    7 KB (1,177 words) - 08:34, 8 October 2014
  • * Transfer ** Multi-stage [[chunk]] transfer
    1 KB (160 words) - 10:44, 23 September 2016
  • .... A lint tester would help people write standard code for dictionaries and transfer files. ...at least check [[lttoolbox]] (dix) dictionary data, perhaps also transfer rules. The [[Apertium New Language Pair HOWTO]] should introduce most of the term
    5 KB (789 words) - 10:36, 31 May 2016
  • <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
  • ...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
  • ...rchunk (see "advanced transfer" in the official documentation). Interchunk transfer uses 3 steps and cascaded interchunk uses more than 3. ...ia.org/wiki/Parse_tree Parse tree on Wikipedia]. 1-stage transfer, 3-stage transfer, and n-stage cascaded interchunk are all shallow.
    4 KB (669 words) - 14:12, 6 July 2012
  • ...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
  • ...share a prefix ''cant-''. Therefore, both Apertium's tagger and structural transfer assume that the [[lexical form | lexical forms]] corresponding to these [[s ...ed for more languages, we need to modify the part-of-speech tagger and the transfer.
    6 KB (935 words) - 13:49, 21 August 2018
  • 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
  • ...cal methods: it takes only two smaller corpora and a dictionary containing rules to conjugate verbs and to match nouns and adjectives. ...nt languages. New language pairs can be added by creating dictionaries and rules containing linguistic data in XML format.
    15 KB (2,339 words) - 00:41, 4 June 2018
  • ==Transfer== ...constructions and turn them into their Turkish equivalents. Many of these rules cover constructions that are analytic in Qırımtatar and synthetic in Turk
    4 KB (551 words) - 23:52, 28 August 2017
  • ==Transfer== ==== SOV to SVO transfer ====
    14 KB (2,140 words) - 15:42, 30 November 2010
  • Vi anvender 1-trins "shallow transfer" med 17 transferregler. Yderligere oplysninger kan findes i artiklen "Shallow-transfer rule-based
    9 KB (1,406 words) - 20:34, 29 October 2010
  • <transfer default="chunk"> <section-rules>
    24 KB (709 words) - 12:00, 31 January 2012
  • 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
  • ...13/08&mdash;19/08 || - || || - || - || Disambiguation and transfer. ...al variants added, some translation mistakes ironed out, a cpl of transfer rules
    6 KB (625 words) - 16:54, 1 July 2013
  • ...tal that people can apply and suggest new words, or new symbols,<br>or new rules but with a interface that guide for end users can do it. === Transfer Rules (Future, only for Post ideas) ===
    4 KB (640 words) - 21:20, 2 April 2009
  • ...ing entries and counting transfer rules, but might be extended to count CG rules as well. It can be run: This will show the count of rules per file, and the entry count per file. It also shows the totals and unique
    12 KB (1,931 words) - 17:06, 24 October 2018
  • Apertium structural transfer rules are currently encoded in XML-based formats. These are very overt and clear, ...rrent XML-based language, allows for a graphical, intuitive editing of the rules, and writes compilable .t1x, .t2x or .t3x files)
    1 KB (162 words) - 01:11, 18 August 2015
  • .... I have worked on adding vocabulary, disambiguation rules in CG, transfer rules and lexical selection. ! CG Rules
    2 KB (335 words) - 10:29, 23 August 2016
  • ...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
  • ...k the lemmata of verbs that can be used in separable contexts. We then use rules to say for example: ...dealt with either in transfer or pre-transfer. If it was dealt with in pre-transfer,
    8 KB (1,265 words) - 08:11, 2 January 2016
  • ...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
  • '''Constraint grammar and transfer rules''' ...ifferent lexical meanings based on the grammatical and lexical context. CG rules work both for disambiguation within one part of speech and between words of
    4 KB (570 words) - 18:43, 23 August 2016
  • However, in some cases we might like attributes to be available to transfer that we don't want to put in our morphological analyser or CG. So the idea is that we have a separate file (or it can go in the transfer file), which allows us to define arbitrary attributes and have them filled
    2 KB (318 words) - 12:25, 5 February 2014
  • | <code>apertium-sme-fin.sme-fin.dix</code> || Transfer lexicon / Bilingual dictionary || | <code>fin-sme.autobil.bin</code> || Compiled transfer lexicon ||
    16 KB (2,457 words) - 08:19, 12 April 2017
  • ...vernance" often mismatches between the the two languages, so some transfer rules will be required. ...st up the coverage - they seem to be quite frequent!) and work on transfer rules if they are needed.
    8 KB (1,205 words) - 21:50, 19 July 2012
  • ==Transfer rules==
    2 KB (248 words) - 13:34, 10 December 2010
  • * Write transfer rules for function words * Write transfer rules for nominals
    4 KB (423 words) - 17:08, 14 June 2018
  • ...hrase co-ordinators from noun phrase co-ordinators lets you write transfer rules to merge two co-ordinated NPs. ...nting part of it can prove useful in writing transfer or lexical selection rules.
    7 KB (922 words) - 08:16, 8 October 2014
  • ...th the Ordbank, and the constraint grammar, and wrote a series of transfer rules. ...en another week converting the Oslo-Bergen tagger. Three weeks on transfer rules, and then another three weeks expanding the dictionaries. Two weeks were th
    12 KB (1,679 words) - 12:00, 31 January 2012
  • ...th the Ordbank, and the constraint grammar, and wrote a series of transfer rules. ...en another week converting the Oslo-Bergen tagger. Three weeks on transfer rules, and then another three weeks expanding the dictionaries. Two weeks were th
    12 KB (1,683 words) - 08:42, 10 May 2013
  • ==Editing XML (dix, transfer rules) in vim==
    2 KB (258 words) - 19:35, 23 March 2020
  • ===Visual interface for editing transfer rules===
    2 KB (200 words) - 08:21, 13 January 2015
  • ...th the Ordbank, and the constraint grammar, and wrote a series of transfer rules. ...en another week converting the Oslo-Bergen tagger. Three weeks on transfer rules, and then another three weeks expanding the dictionaries. Two weeks were th
    12 KB (1,683 words) - 11:00, 30 October 2015
  • ...k. Use the relations GF returns (all of which are hard-coded for different rules). Bonus: use closely related language treebanks in UDPipe; transfer the lemmas, assume the POS tags remain the same (reasonable assumption). Us
    4 KB (657 words) - 08:58, 3 April 2017
  • ===Transfer rules=== Adding to section <section-rules>
    2 KB (240 words) - 09:55, 24 April 2018
  • | 142 || apertium-preprocess-transfer doesn't allow DOCTYPE declaration.... | 140 || apertium-transfer -b outputs tl tag when asked for sl tag if sl tag empty...
    12 KB (1,254 words) - 22:08, 7 March 2018
  • ...', but it's un- or under-documented how this should be done using apertium-transfer. <transfer default="chunk">
    2 KB (209 words) - 11:06, 24 March 2012
  • ==Transfer== * [[A long introduction to transfer rules]]
    2 KB (182 words) - 08:35, 16 May 2013
  • This page provides general documentation on the transfer rules used in the Romanian-Catalan pair. The tables are generated from the data a === Extra transfer (T4X) ===
    14 KB (1,989 words) - 10:06, 28 November 2018
  • The t2x rules may have completely "correct" blank handling in that they output all input # Transfer modules have to treat the inline-blanks differently from other superblanks
    10 KB (1,674 words) - 15:22, 26 May 2020
  • [[VM for transfer|In English]] | align=center | Header || <code>#<assembly><br /> #<transfer default="chunk"></code> || align=center | ---- || Cette section établit le
    14 KB (2,144 words) - 14:05, 7 October 2014
  • ...ning corpus by taking into account the patterns detected by the structural transfer module, and translates to the target language all possible disambiguation p ...ansfer rules (right now, it only "understands" one-level, shallow-transfer rules).
    2 KB (260 words) - 19:55, 24 March 2020
  • ..., CG performance, regression and pending tests targeted mainly at transfer rules, a “gold standard” parallel corpus to measure the WER and to always hav * transfer
    4 KB (603 words) - 21:20, 31 August 2015
  • apertium-transfer $DATA/trules-$DIRECTION.xml $DATA/trules-$DIRECTION.bin $AUTOBIL |\ apertium-transfer $DATA/$DIRECTION.t1x $DATA/$DIRECTION.t1x.bin $DATA/$DIRECTION.autobil.bi
    12 KB (1,625 words) - 08:20, 8 October 2014
  • ...pertium-preprocess-transfer (or make), then you can check out the relevant rules by doing e.g. (exchanging apertium-dan-nor.nor-dan.t1x for your transfer file)
    1 KB (187 words) - 19:29, 13 December 2016
  • Lexical transfer: Lexical selection rules:
    6 KB (412 words) - 23:31, 31 January 2020
  • 2. The current .twol file is empty. Need to add all the morphographemic rules to it. ...ive clause appear.There are few transfer rules in the bidix. More transfer rules need to be added to all .t1x .t2x and .t3x files.
    4 KB (669 words) - 14:42, 13 August 2018
  • ...analyser for turkish, a generator for Azerbaijani, a bidix and a set of CG rules. ; Rules
    7 KB (1,091 words) - 18:40, 25 August 2011
  • ...s also contained in the transducers generated by <code>apertium-preprocess-transfer</code>. ...e rules which generate different output in different situations as well as rules which generate multiple outputs, the simplest way do deal with them is to t
    3 KB (522 words) - 20:14, 31 July 2019
  • ...y in a way which 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 ...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
  • The '''bilingual dictionary''' (also known as '''bidix''' and '''transfer lexicon''') contains translation between two languages. It is one of the ma ...you will find some notes on how to work with bilingual dictionaries (or ''transfer lexica'') in Apertium, they aren't complete but should give an overview of
    7 KB (1,244 words) - 16:41, 17 March 2018
  • ...n-line'' because of the high failure rate, due to either disambiguation or transfer, just incomplete entries. apertium-transfer /home/fran/local/share/apertium/apertium-is-en/apertium-is-en.is-en.t1x /h
    9 KB (1,470 words) - 11:28, 24 March 2012
  • ...cy wykorzystuje słowniki oraz płytkie reguły transferowe (shallow transfer rules). Zasadniczą różnicą pomiędzy głębokimi i płytkimi zasadami jest to ...lementowanie zasad dla rzeczowników. Pliki tego typu posiadają własne DTD (transfer.dtd) znajdującym się w pakiecie Apertium. Gdy zaistnieje potrzeba zaimple
    36 KB (5,643 words) - 07:04, 16 February 2015
  • ...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 ...ream processor (see [[Apertium stream format]]) for the output of apertium-transfer (both default/chunk possibilities) that parses character by character.
    2 KB (262 words) - 11:19, 9 February 2015
  • * transfer rules as constraints (dank idea): ** es-ca will have a (structural) transfer rule X
    1 KB (203 words) - 12:56, 29 January 2018
  • ...ictionaries, improving disambiguation, and writing new structural transfer rules. ...frequently mistranslated and that can be easily repaired with a structural transfer rule
    2 KB (213 words) - 19:48, 24 March 2020
  • ...used to discard possible analysis of the word, according to the following rules: ...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
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    22 KB (2,532 words) - 11:36, 30 July 2018
  • This should be fairly straightforward, then we write rules that say "Choose the feminine possessive when the noun that follows is subj * <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 should
    6 KB (1,000 words) - 07:12, 8 October 2014
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for
    11 KB (952 words) - 21:49, 3 September 2017
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    10 KB (1,263 words) - 06:04, 23 December 2014
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    22 KB (2,520 words) - 23:09, 22 December 2014
  • ...own words will give a better indication of "best-case" working of transfer rules. (Stats pages currently do not show number of CG or transfer rules.)
    9 KB (1,180 words) - 19:52, 26 April 2018
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    19 KB (2,201 words) - 09:21, 9 December 2019
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...for X→Y translation with the addition of a CG for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    12 KB (1,308 words) - 19:27, 27 August 2017
  • =Malayalam Sandhi Rules Implementation(Handling agglutination )= =Transfer Rules=
    14 KB (1,774 words) - 15:47, 18 August 2014
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for
    34 KB (3,543 words) - 06:44, 18 April 2020
  • ...ertium-kaz-rus]. It contains only the kaz→rus direction, recycled transfer rules from tat–rus,  and a few words in the dictionary, but the KazNU team has Transfer rules in tat-rus require the addition of some paradigms to bilingual dictionary e
    1 KB (228 words) - 18:24, 19 August 2017
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...for X→Y translation with the addition of a CG for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    9 KB (987 words) - 23:25, 22 December 2014
  • '''Transfer rules (Romanian to Catalan):''' 118 (T1X), 7 (T2X), 1 (T3X) '''Transfer rules (Catalan to Romanian):''' 33 (T1X), 5 (T2X), 1 (T3X), 1 (T4X)
    538 bytes (72 words) - 10:08, 28 November 2018
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    20 KB (2,336 words) - 18:10, 14 April 2015
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    32 KB (3,684 words) - 06:16, 28 December 2018
  • ...translation quality. This will involve working with dictionaries, transfer rules, scripting, corpora. The objective is to make an Apertium language pair sta ** Add all the words, and cover all the structures with transfer rules.
    2 KB (378 words) - 19:33, 15 March 2017
  • <spectie> --- maybe make LRX rules for the differences described on the wikipedia page http://en.wikipedia.org * transfer, and transfer examples in both directions (Hrvoje)
    2 KB (223 words) - 15:58, 23 April 2013
  • |Sranan rlx rules |Sranan-English t1x rules
    4 KB (543 words) - 21:59, 3 September 2017
  • ...yntax to other Apertium modules (dictionaries, lexical selection, transfer rules, etc). ...] could be used as reference implementation, as it handles similar type of rules, but it looks to the source language (left part) to decide over the target
    1 KB (234 words) - 19:48, 24 March 2020
  • Recursive transfer bytecode files are written using <code>Lttoolbox/compression.h</code>. The Number of input-time rules
    9 KB (1,322 words) - 01:30, 17 February 2020
  • ** Number of disambiguation rules ** Number of lexical selection rules
    2 KB (246 words) - 02:32, 1 June 2019
  • * Making constraint grammar rules more CG-like * Write rules to do initial mutations for generation.
    2 KB (381 words) - 09:59, 8 May 2011
  • ...nd finally emit an epsilon symbol as flag diacritics defined by constraint rules do, or process the input and output the transducer's computation. ...at makes possible to avoid the possibly infinite definition of not regular rules in a dictionary to work with more complex forms of inflection.
    6 KB (842 words) - 06:41, 20 October 2014
  • ...separate lexcs and twols (.lat and .cyr) with the continuation lexica and rules and all, though you may be able to get by with one twol considering how sim ...ambiguation rules to be as script-agnostic as possible. For word-specific rules, make a version for each script?
    4 KB (601 words) - 17:49, 8 March 2018
  • * Constraint grammar of Tatar containing at least 1000 rules, which makes 90-95% of all words unambiguous, with at least 95% retaining t |colspan="4" style="text-align:center"| transfer rules for pending wiki tests (focus on phrases and clauses, not single words)
    8 KB (1,006 words) - 12:48, 9 March 2018
  • # 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
  • # lexical transfer # structural transfer
    5 KB (816 words) - 02:32, 13 February 2018
  • ...ok really like multiword expressions, other times they look like syntactic transfer, most of them have probably have some kind of fixed lexical element. ...sy to translate word-for-word, but also quite annoying to have in transfer rules.
    1 KB (207 words) - 07:51, 9 October 2014
  • ...tax in analysis, the clitics could simply be output in order, and transfer rules written accordingly. ...best to have the same pattern output regardless of clitic, for the sake of transfer. The third person singular as object is implied when there is no pronominal
    2 KB (357 words) - 12:40, 1 October 2016
  • To transfer to the application Apertium is a shallow-transfer machine translation system, which uses finite state transducers for all of
    8 KB (1,230 words) - 06:02, 5 February 2019
  • ...aches that have been taken, both relying on an intermediate dictionary and transfer format which is then converted by an xsl stylesheet into the "real" .dix fi ...ix and parametrized dictionaries]] on ''variants'' in monodix and transfer rules
    1 KB (170 words) - 18:26, 3 September 2011
  • To transfer to the application Apertium is a shallow-transfer machine translation system, which uses finite state transducers for all of
    8 KB (1,242 words) - 20:46, 8 February 2020
  • ...s useful for machine translation (MT): bilingual dictionaries and transfer rules. The induction systems and open linguistic data can be used with the [[Aper ...bilingual resources from aligned parallel corpora: application to shallow-transfer machine translation". ''Machine Translation'' (to appear)
    8 KB (1,253 words) - 09:42, 6 October 2014
  • * The tool validates XML dictionary and transfer files. * Support for trace of transfer/interchunk - with links to the applied rules - also works for online modes
    10 KB (1,605 words) - 08:55, 22 October 2019
  • * Think of rules to fix frequent disambiguation problems ;Slovenian→Spanish transfer
    4 KB (472 words) - 16:41, 7 June 2011
  • # fix tags of "be" in transfer # transfer rules to get tags from beAdjVerb to new be{{tag|v}}
    14 KB (567 words) - 20:03, 24 March 2020
  • ** Transfer rule files You need a <code>Makefile.am</code> which contains the build rules, and a <code>configure.ac</code> which contains the dependencies.
    972 bytes (144 words) - 12:09, 26 September 2016
  • ...ang2015-rakhimova.pdf Study of the problem of creating structural transfer rules and lexical selection for the Kazakh-Russian machine translation system on ...pertium-turklang-2015-papers/turklang2015-karibayeva.pdf Lexical selection rules for Kazakh-to-English machine translation in the free/open-source platform
    13 KB (1,710 words) - 20:32, 30 August 2018
  • This page provides general documentation on the transfer rules used in the English-Catalan pair. The tables are generated from the data an |Adds 'més' before an adjective in comparative or superlative form (for rules with two adjectives).
    45 KB (7,840 words) - 10:56, 18 September 2017
  • ...ved by means of a number of transfer rules. We can probably generate these rules by enumerating a large number of possible combinations of noun phrases and
    1 KB (161 words) - 05:46, 13 January 2013
  • ...ated aligned segments. Ony of the obstacles to inducing effective transfer rules from parallel corpora is lack of literalness in translation. For example, f When making rules, we're more interested in "literal" translations, so for example:
    2 KB (392 words) - 13:47, 18 March 2009
  • ...nvolve writing linguistic data, including morphological rules and transfer rules — which are specified in a declarative language. A good intro would be to
    6 KB (1,010 words) - 14:44, 25 February 2020
  • ...aries (<code>.lexc</code> and <code>.twol</code> files) and disambiguation rules (<code>.rlx</code> files) are no longer kept in the bilingual module, and s ...x</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
  • ** Add lexical selection rules and transfer rules as needed
    2 KB (243 words) - 21:22, 19 August 2015
  • ...an, sme, …) don't get testvoc problems, and possibly change their transfer rules/bidixes (and in some cases the easiest way is to update all the other other
    22 KB (3,325 words) - 14:06, 12 March 2018
  • === Rules === ''Comment'' : just transfer the lexical unit
    323 bytes (27 words) - 16:41, 15 August 2011
  • * Add transfer rules, etc.
    2 KB (233 words) - 07:41, 14 August 2018
  • ...pens after bidix lookup (word-translation), but before structural transfer rules. See [[Lexical selection]] for more information.
    4 KB (620 words) - 18:06, 26 September 2016
  • ...ranslation output by the structural-transfer module to see if the applying rules with new apertium were better or worse than the old apertium. We found out
    2 KB (348 words) - 10:16, 24 October 2018
  • You can also write lexical rules, so for example in Afrikaans, the word "deur" is ambiguous, one meaning is (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
  • [[Category:Writing transfer rules]]
    4 KB (706 words) - 07:05, 8 October 2014
  • * Having zero-context rules in your .lrx files. Now you can just put the weights directly in your bilin ...efault translation as "1.0" and then all others as >1.0 ... because of how transfer works, it will always take the first, which will be the one with the lowest
    2 KB (353 words) - 09:32, 30 January 2019
  • ...al transfer, so if input is a determiner followed by a noun, and there are rules for "det", "n", and "det n", the "det n" rule will match.
    676 bytes (102 words) - 11:07, 12 September 2014
  • [[Category:Writing transfer rules]]
    16 KB (2,435 words) - 07:05, 8 October 2014
  • This page is intended to be a collection of solutions to common transfer problems. It is sorted vaguely be complexity, so it could potentially also These rules will match a determiner, 0 or more adjectives, and a noun and make all the
    2 KB (343 words) - 16:48, 6 August 2019
  • : should be possible to make transfer rules like "NP sein am V.inf" => "NP be V.progressive"
    3 KB (442 words) - 00:36, 5 January 2013
  • ...r to avoid having to write structural transfer (i.e., .t1x, .t2x and .t3x) rules in raw XML which is very overt and clear, but clumsy and hard to write. Bef
    2 KB (324 words) - 11:37, 16 February 2016
  • * [[Preparing to use apertium-transfer-tools]] * [[How to get started with lexical selection rules]]
    5 KB (599 words) - 19:04, 17 February 2020
  • ==Transfer rules==
    2 KB (258 words) - 20:15, 5 February 2017
  • ...data to induce the part-of-speech tagger and an initial set of translation rules from monolingual and bilingual corpora.
    8 KB (1,254 words) - 16:54, 12 March 2009
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below.
    6 KB (595 words) - 23:13, 22 December 2014
  • ...data to induce the part-of-speech tagger and an initial set of translation rules from monolingual and bilingual corpora.
    9 KB (1,542 words) - 13:38, 10 February 2010
  • * XXX-YYY.t1x.bin :: the compiled transfer rules (stage 1 / chunking, or the only stage if no chunking used) when translatin
    890 bytes (126 words) - 10:10, 14 March 2017
  • * [[Regression test]]s – "isolated" tests of transfer rules
    507 bytes (65 words) - 08:18, 2 March 2016
  • ...mproving the engine, improved source-language analysis, improved bilingual transfer, new end-user application, improve existing end-user application, easing la ...k will be frozen and we will report to Google, to proceed according to the rules of GSoC.
    10 KB (1,500 words) - 16:23, 18 February 2016
  • 16th August: Implement transfer rules in both directions based
    2 KB (208 words) - 16:53, 17 June 2010
  • This could make for a number of good transfer rules. ''Para'''t''' haya'' -> You have money. The pattern would be like nominal<
    5 KB (855 words) - 19:23, 27 August 2017
  • ...for X→Y translation with the addition of a CG for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    18 KB (2,312 words) - 18:25, 18 September 2016