Search results

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

• User:Pmodi/GSOC 2020 proposal: Hindi-Punjabi
  ...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
• User:Aidana/Proposal
  .... 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
• Matxin 1.0 New Language Pair HOWTO
  There are two main issues with transfer in this case, the first is re-ordering, from <code>OVS → SVO</code>, the ...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
• Weighted transfer rules at GSoC 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
• Workflow reference
  ===Lexical transfer/Translation/bidex lookup=== This tool runs the bilingual dictionary transfer,
  29 KB (4,687 words) - 16:28, 5 June 2020
• Курсы машинного перевода для языков России/Session 6
  ...ransfer module is necessary. This session describes the Apertium 3+ level transfer system which was designed to allow easier treatment of longer patterns, and ===Chunking-based transfer===
  14 KB (1,969 words) - 12:00, 31 January 2012
• Helsinki Apertium Workshop/Session 6
  ...ransfer module is necessary. This session describes the Apertium 3+ level transfer system which was designed to allow easier treatment of longer patterns, and ===Chunking-based transfer===
  14 KB (1,975 words) - 08:36, 10 May 2013
• Tartu Apertium Course/Session 6
  ...ransfer module is necessary. This session describes the Apertium 3+ level transfer system which was designed to allow easier treatment of longer patterns, and ===Chunking-based transfer===
  14 KB (1,975 words) - 10:58, 30 October 2015
• User:Rroychoudhury/GSoC 2020 Proposal
  ...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
• Hectoralos/GSOC 2019 proposal: Catalan-Italian and Catalan-Portuguese
  ...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
• User:Rafi kamal/Application
  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
• The quick and dirty guide to making a new language pair
  ...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
• User:Marcriera/proposal
  ...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
• Romanian and Catalan/GSOC 2018
  ===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
• User:Lylax2/proposal2017
  ...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
• User:Uliana/gsoc-propuesta
  - 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
• User:Srj31/GSOC 2020 proposal:Bengali-Hindi pair
  ...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
• English and Catalan/Workplan
  * Write documentation on the current status of transfer rules * Write documentation on the current status of transfer rules
  5 KB (506 words) - 14:56, 28 August 2017
• Constraint-based lexical selection module
  ...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
• Narimann/GSOC 2019 proposal: Kazakh-Turkish and Turkish-Kazakh
  * Write new transfer rules * Write transfer rules (Turkish > Kazakh)
  8 KB (1,094 words) - 13:10, 14 April 2019

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