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

  • 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
  • ...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
  • 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
  • how to write transfer rules [[Category:Transfer]]
    5 members (0 subcategories, 0 files) - 20:36, 24 March 2020
  • ==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

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
  • ...r getting the final few percent in closely-related languages. A tree-based transfer would allow us to work on real syntactic constituents, and probably simplif ...ght eventually make Apertium run on J2ME devices. See also: [[Bytecode for transfer]] || C++ and for the bytecode Java or Javascript ||
    71 KB (10,374 words) - 21:14, 18 January 2021
  • 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
  • ...y would need to be addressed in the [[Apertium pipeline]] (morph analysis, transfer, etc). Use a grammar book/resource for inspiration. Each difference shoul |title=Add a transfer rule to an existing translation pair
    397 KB (52,731 words) - 11:22, 10 December 2019
  • 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
  • ...ng and correcting transfer rules, lexical selection and constraint grammar rules, also adding vocabulary in monolingual and bilingual dictionaries. I am a 4
    7 KB (1,078 words) - 05:24, 13 May 2014
  • ...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
  • '''GSOC 2019 : Extend weighted transfer rules'''[http://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code#Extend_wei ...tium , and that encouraged me to choose the idea "Extend weighted transfer rules" to continue our work, extend, integrate and deploy the full module.
    18 KB (2,903 words) - 22:18, 8 April 2019
  • ...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.
    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,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
  • .... I am planning to expand the dictionary, create more transfer and lexical rules. ...produce translation with high quality, bigger vocabulary and more transfer rules. Resources could be used for another language pairs, where the Kazakh is so
    9 KB (1,088 words) - 19:28, 24 March 2016
  • ...languages, the hin-pan bilingual dictionary and writing suitable transfer rules to bring this pair to a releasable state. * Improvements(current rules and word pairs) and additions to hin-pan bidictionary
    27 KB (4,091 words) - 19:32, 4 June 2020
  • 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
  • ...I am most familiar with , and it would be interesting to develop transfer rules for building a bridge between the two so that people can utilise this for f ...teria of sentiment, which will help to disambiguate lexicons by generating rules based on patterns incorporating sentiment of words. (.lrx file)<br>
    16 KB (2,215 words) - 14:49, 31 March 2020
  • ...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
  • I'll write lexical selection rules for disambiguation of bidix output. These rules will be used by Apertium's lexical selection module. ==== 4. Adding transfer rules ====
    10 KB (1,432 words) - 10:24, 15 May 2014
  • ...es and public domain books will be used. However, as the existing transfer rules lack any kind of organization, code refactoring will be absolutely necessar ...is to improve the language pair in the EN>CA direction, there will be some rules added to make it work better in the opposite direction too.
    13 KB (1,713 words) - 13:05, 29 May 2017
  • ...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
  • ...ikit-learn, lxml, Django), R, Octave, Bash, Matxin(Apertium with syntactic transfer), Javascript(Jquery, D3) ...election. Work on rudimentary transfer rules, as well as begin on transfer rules for verbs.
    10 KB (1,554 words) - 08:37, 4 April 2017
  • - try to write transfer rules and lexical selection rules; ...n classes of words ('''nouns'''): expanding dictionaries, writing transfer rules.
    11 KB (1,652 words) - 15:56, 24 March 2016
  • ...nd Hindi are similar in various linguistic aspects, they will have similar rules thus machine translation would give correct sentences if done correctly. H ...guage pairs and their rules, to further understand how to create efficient rules
    12 KB (1,663 words) - 12:53, 31 March 2020
  • * 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
  • ...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
  • * 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,387 words) - 16:27, 31 March 2020
  • [[User:Ggregori/Application|VM for the transfer module - Application]] '''Github repository (python):''' [https://github.com/ggm/vm-for-transfer]
    15 KB (2,393 words) - 05:10, 27 August 2011
  • ...released, it contains a basic but decent bilingual dictionary and transfer rules for the Romanian > Catalan direction re-used from a very similar pair, Roma * Rewrite and expand the transfer rules for Romanian > Catalan to take advantage of chunks
    11 KB (1,500 words) - 15:44, 30 April 2018
  • *Grammar rules - [https://en.wikipedia.org/wiki/Swahili_grammar Wikipedia's Grammar Rules]<br/>
    6 KB (988 words) - 13:21, 31 March 2020
  • * Started sample Lexical selection rules; |Focus on transfer rules
    10 KB (1,179 words) - 11:51, 31 August 2021
  • ...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
  • '''Prototype recursive transfer implementation''' ...sfer rules part. I think this is helpful to understand deeper the transfer rules.
    7 KB (1,097 words) - 02:39, 21 March 2014
  • * dix-mode, for XML dictionary and transfer editing == XML (dix, transfer, …) editing ==
    16 KB (2,637 words) - 12:46, 23 March 2022
  • Prototype recursive transfer implementations ...transfer module in Apertium by adding a support of the recursive transfer rules.
    6 KB (948 words) - 19:03, 21 March 2014
  • **A set of post-generation rules ...system of structural transfer in three steps. I consider the new recursive transfer very promising, and I indeed want to use in the new version of the French-C
    14 KB (2,071 words) - 12:46, 30 March 2020
  • **No rules to handle transitive and intransitive verbs **Listing intransitive verbs and adding transfer rules to handle transitive/intransitive verbs. (ongoing)
    11 KB (1,617 words) - 11:06, 29 April 2017
  • ...bn-en to a wide coverage of Bengali wiki. Then I’ll focus on the transfer rules and finally, the testvoc. * Writing the transfer rules to complete the transfer system
    9 KB (1,374 words) - 07:51, 9 April 2011
  • The current way of writing the dictionary and the transfer rule is in the format of xml which may be difficult for some developers and ...way which will be in text format to write the dictionary and the transfer rules.
    12 KB (1,985 words) - 14:22, 21 March 2014
  • ...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
  • ...h, so I'm interested in developing the bilingual dictionaries and transfer rules. This would really nice to have, especially since speakers of both language * Lexical selection and transfer rules for nhi-azz and azz-nhi
    9 KB (1,296 words) - 17:42, 4 April 2023
  • ===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
  • *Grammar rules - [https://en.wikipedia.org/wiki/Swahili_grammar Wikipedia's Grammar Rules]<br/>
    4 KB (586 words) - 05:03, 19 May 2020
  • ...ch-Occitan pair, even if this will make it somewhat difficult to reuse the rules of the French-Catalan pair. ...and understanding of Apertium (chiefly the lexical selection and transfer rules).
    13 KB (1,949 words) - 20:05, 26 March 2018
  • ...[Ideas_for_Google_Summer_of_Code/Weighted_transfer_rules|Weighted transfer rules]]. ...ides Russian and English anyway). Francis pointed at the Weighted transfer rules and I really liked it, because, personally, I hate when ambiguity has to be
    10 KB (1,671 words) - 18:37, 24 March 2016
  • The project aims to speed up the [[VM for transfer]] code (the transfer step being the slowest of the experience (so a good starting point for me would be VM-for-transfer). Also, I met on IRC some really
    14 KB (2,387 words) - 16:36, 20 March 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
  • ...he Anaphora Resolution tool will be language agnostic''' and there will be rules which should work for most related languages. Pronouns are present in a lot After this, it will pass through transfer and we can add transfer rules to pick the correct pronoun/adjective based on the antecedent, if needed.
    26 KB (4,048 words) - 18:50, 18 March 2020
  • ...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
  • ...ained with relatively uncomplicated rules. Moreover, the CG disambiguation rules can be easily expanded and adapted for use on both languages, so the result ...also improve the Serbo-Croatian morphological analyser and disambiguation rules, providing a great free resource for three languages, alltogether spoken by
    7 KB (1,159 words) - 11:30, 7 April 2012
  • 3. Added 8 rules which give me correct translations for:<br/> * and other rules for dealing with the infitive form of a verb, and handling the [https://en.
    8 KB (1,262 words) - 07:04, 27 March 2020
  • 3. Added 8 rules which give me correct translations for:<br/> * and other rules for dealing with the infitive form of a verb, and handling the [https://en.
    7 KB (1,168 words) - 09:53, 28 March 2020
  • 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
  • • Writing Lexical selection rules for better translation accuracy; * Lexical selection rules;
    6 KB (854 words) - 15:35, 20 April 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
  • ...t a lot of changes in the quality of the result. This got me interested in transfer rule based machine translation ability. With the help of the Apertium team, ...through a lot of documentation of Apertium about writing transfer grammar rules, monodix basics, and testing the dictionaries. I think I will be able to gr
    10 KB (1,482 words) - 22:05, 21 May 2014
  • ...selection module(s) should allow both the use of rules and of statistics. Rules for things we "know", statistics for those we don't. === Inferring rules from collocations ===
    51 KB (7,047 words) - 08:49, 9 June 2011
  • ...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
  • * Convert any remaining eng->spa rules ...ator compliant with initial specifications, and complete end->spa transfer rules
    14 KB (2,141 words) - 21:26, 13 August 2019
  • ...he use of apertium-separable. More work needs to be done lexical selection rules and few more tasks(See #Future_Work). The results on Wikipedia articles wer ===Transfer Rules===
    10 KB (1,507 words) - 10:49, 7 September 2020
  • ...t work" in every domain, and only a few specific cases per domain may need rules written for them. ...ate each use and find their Bengali translations using a set of linguistic rules. Some Hindi pronouns are used to demonstrate both animate and inanimate nou
    13 KB (1,923 words) - 13:52, 3 April 2017
  • ...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,721 words) - 07:55, 20 May 2013
  • ...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
  • * Building the transfer rules for the HIN-MWR pair. * Getting familiar to the syntax for writing transfer rules.
    7 KB (1,043 words) - 15:03, 19 April 2023
  • ...nance]]. I'm much less certain about similar contributions to monodix. For transfer though you could probably make something that shows the tree that gets buil Tricky things: non-projective stuff? transfer?
    6 KB (972 words) - 18:06, 23 December 2022
  • | 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
  • ...m up to release quality, which will involve writing and refining rules for transfer, expanding dictionaries, testvoc and lexical selection that will result in ...big part of what's involved is [[testvoc]], not just writing and refining rules. Probably expanding dictionaries is fairly important as well. —[[User:Fi
    4 KB (614 words) - 13:00, 7 April 2019
  • ...ambiguation in a finite-state manner. Since the most common disambiguation rules can be expressed in a finite-state way, this will greatly improve speed of ...es to an Apertium input stream. The syntax will mostly resemble Apertium's transfer or LanguageTools' disambiguator module, since it is the most natural syntax
    12 KB (1,894 words) - 19:10, 5 April 2012
  • ...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
  • ...e amount of parallel translated (mvf-khk) text with ready a vocabulary and rules (for example [http://www.cjvlang.com/mongol/index.html]). * Learn Constraint Grammar and Lexical Selection rules.
    11 KB (1,714 words) - 13:51, 28 March 2018
  • ...lenges to solve which occur during machine translation for example lexical transfer and reordering. Also When I talked to people already working on Apertium fo ...r during transfer) based on the dependency tree (this would not do lexical transfer, concordance or anything else, just LU reordering). <br /><br />
    14 KB (2,232 words) - 19:03, 7 April 2011
  • ....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
  • Both sme-nob and nno-nob have lots of postchunk rules that match names like "adj_adj_n_n" – this means a four-word chunk, two a ==WISH GRANTED: Fallthrough option in transfer==
    17 KB (2,774 words) - 07:27, 20 January 2023

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