Search results

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

• User:Lguyogiro/GSoC2023Proposal
  ...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
• English and Catalan/GSOC 2017
  ===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
• Format handling
  ...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
• User:Eden/GSOC2020 Swahili-Lingala
  *Grammar rules - [https://en.wikipedia.org/wiki/Swahili_grammar Wikipedia's Grammar Rules]<br/>
  4 KB (586 words) - 05:03, 19 May 2020
• User:Capsot/Proposal oci-fra/fra-oci Translator
  ...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
• User:Nikita Medyankin/GSoC 2016 WTR Proposal
  ...[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
• Apertium-recursive/Formalism
  ...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
• User:Asfrent/Application
  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
• Task ideas for Google Code-in
  |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
• English and Catalan
  '''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
• Northern Sámi and Norwegian
  ...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
• Romanian and Catalan/Workplan
  * 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
• User:Khannatanmai/GSoC2019Proposal
  ...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
• Using weights for ambiguous rules
  ...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
• User:Eden/GSOC2019 English-Lingala
  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
• User:Krvoje/Application2012-sh-sl
  ...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
• User:Prondubuisi/GSOC 2020 proposal:English-Igbo pair
  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
• Testvoc
  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
• User:Kamush/GSoC2021Proposal
  • Writing Lexical selection rules for better translation accuracy; * Lexical selection rules;
  6 KB (854 words) - 15:35, 20 April 2021
• Ideas for Google Summer of Code/Automatic blank handling
  ...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

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