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.
- | 4 || 4 junh—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
- ...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 grammatical14 KB (2,007 words) - 03:06, 27 October 2013
- ...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 is7 KB (1,110 words) - 11:34, 23 August 2016
- ....af-en.t1x || Afrikaans—English first stage transfer file (transfer) |apertium-en-af.af-en.t2x || Afrikaans—English second stage transfer file (interchunk)5 KB (583 words) - 11:17, 18 November 2013
- ...|| 15:00—17:00 || '''Practical''': Writing rules for morphological disambiguation ...an="6"| [[Helsinki Apertium Workshop/Session 4|4: Lexical transfer]] || '''Practical''': Dictionary work8 KB (720 words) - 15:18, 20 March 2015
- ...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 platform33 KB (4,418 words) - 11:52, 29 December 2021
- ==apertium-transfer-tools== Automatic shallow-transfer rules generation from parallel corpora4 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.bin23 KB (3,704 words) - 11:56, 16 December 2020
- 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 y5 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 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 y6 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
- ...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
- 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 Indi6 KB (923 words) - 17:57, 3 April 2010
- ...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
- *The file with the transfer rules to be used (trules.xml or .t1x file — 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
- ! Transfer goal | Good coverage, insufficient CG rules3 KB (288 words) - 08:30, 23 July 2018
- ...dule to replace the apertium-transfer module(s) which will parse and allow transfer operations on an input. # Propose a transfer rule formalism2 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 ch15 KB (2,237 words) - 12:41, 21 August 2015
- | [[A long introduction to transfer rules]] | [[Preparing to use apertium-transfer-tools]]13 KB (1,601 words) - 23:31, 23 July 2021
- ==Transfer rules English->Esperanto== ===Single word rules English->Esperanto===7 KB (1,105 words) - 01:18, 4 February 2009
- ...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 thi8 KB (1,205 words) - 13:15, 28 August 2011
- ** 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 another5 KB (984 words) - 09:44, 24 August 2012
- !colspan="2"| lexical transfer !colspan="2"| pre-transfer6 KB (873 words) - 14:35, 28 July 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 transl15 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 pr14 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
- === A Simple Set of Rules === !!! Tag rewrite rules33 KB (6,259 words) - 06:07, 1 June 2023
- ;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 re187 KB (21,006 words) - 22:14, 12 November 2012
- * Incorrect transfer direction. ==Transfer==9 KB (1,459 words) - 19:41, 15 May 2021
- 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 rules8 KB (975 words) - 06:42, 23 September 2013
- ...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 tra7 KB (1,057 words) - 21:07, 1 December 2013
