Search results

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

• 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
• 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
• 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
• 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
• 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
• Chebrolutejasvi/GSOC 2020 proposal: Hindi-Telugu
  ...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
• Anaphora resolution module
  ...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
• Emacs
  * dix-mode, for XML dictionary and transfer editing == XML (dix, transfer, …) editing ==
  16 KB (2,637 words) - 12:46, 23 March 2022
• Belarusian and Russian/Final report
  ...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
• Ideas for Google Summer of Code
  ...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
• Ideas for Google Summer of Code/Weighted transfer rules
  ...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
• Apertium-recursive
  ...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
• Introduction aux règles de transfert
  [[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
• Slovenian and Spanish/Final report
  ...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
• 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
• 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

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