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

  • ==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
  • 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.
    28 KB (4,478 words) - 12:25, 17 March 2022
  • ...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

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.
    28 KB (4,478 words) - 12:25, 17 March 2022
  • ...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,302 words) - 12:00, 31 January 2012
  • ...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
  • ...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,856 words) - 06:26, 27 May 2021
  • ===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
  • ===Transfer=== ...from this representation using both bilingual dictionaries and grammatical rules.
    12 KB (1,464 words) - 12:00, 31 January 2012
  • ...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,933 words) - 16:14, 22 February 2021
  • ...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:28, 5 June 2020
  • ...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,164 words) - 20:58, 2 April 2021
  • ===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
  • ...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==
    19 KB (2,820 words) - 15:26, 11 April 2023
  • * 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
  • ...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
  • * dix-mode, for XML dictionary and transfer editing == XML (dix, transfer, …) editing ==
    16 KB (2,637 words) - 12:46, 23 March 2022
  • ...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
  • ...n two existing language modules, focusing on the dictionary and structural transfer ...xpanding the transducers and disambiguation, and writing lexical selection rules and multiword sequences may also be part of the work. The pair may be an e
    23 KB (3,198 words) - 09:15, 4 March 2024
  • ...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
  • ...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">
    6 KB (964 words) - 06:13, 1 June 2023
  • [[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
  • ...ns attribute categories, tag-order rules, tag-rewrite rules, and reduction rules. ...nal names, some of which are included primarily for compatibility with t*x rules. Do not use these directly
    32 KB (5,012 words) - 13:27, 6 September 2023
  • |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,400 words) - 22:30, 18 January 2021
  • ...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
  • ...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
  • ...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
  • ...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
  • ....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
  • ...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
    33 KB (4,418 words) - 11:52, 29 December 2021
  • ...|| &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,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 y
    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 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
  • ...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 Indi
    6 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 &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
  • ! Transfer goal | Good coverage, insufficient CG rules
    3 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 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,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 thi
    8 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 another
    5 KB (984 words) - 09:44, 24 August 2012
  • !colspan="2"| lexical transfer !colspan="2"| pre-transfer
    6 KB (873 words) - 14:35, 28 July 2020
  • == 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
  • {{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
  • ...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 rules
    33 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 re
    187 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 rules
    8 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 tra
    7 KB (1,057 words) - 21:07, 1 December 2013

View (previous 100 | next 100) (20 | 50 | 100 | 250 | 500)